<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 28, 2014 at 9:39 AM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
On 28 Oct 2014, at 09:26, Erik Jan de Wit <<a href="mailto:edewit@redhat.com">edewit@redhat.com</a>> wrote:<br>
<br>
> Hi,<br>
><br>
> I was working on a Oath2 plugin for cordova with the latest swift bits, but using swift for a cordova plugin is not very user friendly. The generated project that gets downloaded when you do a `cordova platform add ios` has to be change by opening Xcode.<br>
><br>
> Things that need to be changed by hand are the following:<br>
> * iOS Deployment target needs to be set to something higher then the 6.0 it’s now at<br>
<br>
</span>would it help if we label which version works with 6.0, which one with 6.1?<br>
<span class=""><br>
> * Bridging-Header.h to Objective-c Bridging Header under the Swift Compiler - Code Generation options<br>
> e.g (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h)<br>
> * the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited) @executable_path/Frameworks”<br>
><br>
> That is just a little to much for a user to do, and I see no way to hook this into the cordova project / plugin configuration. The cordova team are planning to change the way the project is created and how settings are maintained in version 4.0 I’ve created two PR that help that effort, but these have not been merged yet.<br></span></blockquote><div><br></div><div>great way of interacting w/ the Apache Cordova folks! Glad seeing our team is submitting PRs to the core ios project :) </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
<br>
</span>I’m following this PR:<br>
<a href="https://github.com/apache/cordova-ios/pull/104" target="_blank">https://github.com/apache/cordova-ios/pull/104</a><br>
what is the other one?<br>
<span class=""><br>
><br>
> So I propose that we don’t release the plugin, but wait on cordova to update so that manual steps will no longer be needed, or we add a big Notice on how to install use this plugin.<br>
><br>
> WDYT?<br>
<br>
</span>what about doing an early adopter release of the plugin with its demo and blog post explaining the current difficulties (which require manual steps) and talk about what’s next in cordova-ios: workspace instead of just project…</blockquote><div><br></div><div>+1 I like the idea</div><div><br></div><div>Especially since our Cordova OAuth2 plugin is not just about iOS. It's about Android as well.</div><div><br></div><div>I am in line w/ Corinne: mark the iOS side of the OAuth2 plugin as 'experiemental, and release note (or blog) the odd parts. I'd prefer a blog post on Aerogear.org, instead of a private one</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I can hel with testing and blog post.<br></blockquote><div><br></div><div>+1 count me in!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
where is your current demo? is it this repo:<br>
<a href="https://github.com/edewit/aerogear-cordova-cookbook/tree/swift-oauth2-plugin" target="_blank">https://github.com/edewit/aerogear-cordova-cookbook/tree/swift-oauth2-plugin</a><br>
?<br>
<br>
><br>
> Cheers,<br>
> Erik Jan<br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>