Hi, 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. Things that need to be changed by hand are the following: * iOS Deployment target needs to be set to something higher then the 6.0 it’s now at

* Bridging-Header.h to Objective-c Bridging Header under the Swift Compiler - Code Generation options e.g (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h) * the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited) @executable_path/Frameworks” 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.

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. WDYT?

Cheers, Erik Jan _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

On 28 Oct 2014, at 09:26, Erik Jan de Wit <edewit(a)redhat.com&gt; wrote: > Hi, > > 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. > > Things that need to be changed by hand are the following: > * iOS Deployment target needs to be set to something higher then the 6.0 it’s now at would it help if we label which version works with 6.0, which one with 6.1? > * Bridging-Header.h to Objective-c Bridging Header under the Swift Compiler - Code Generation options > e.g (HelloCordova/Plugins/org.jboss.aerogear.cordova.oauth2/Bridging-Header.h) > * the following to LD_RUNPATH_SEARCH_PATHS to "$(inherited) @executable_path/Frameworks” > > 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.

I’m following this PR: https://github.com/apache/cordova-ios/pull/104 what is the other one? > > 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. > > WDYT? 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…

I can hel with testing and blog post.

where is your current demo? is it this repo: https://github.com/edewit/aerogear-cordova-cookbook/tree/swift-oauth2-plugin ? > > Cheers, > Erik Jan > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev