cordova-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shazron Abdullah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CB-5921) Cordova on iOS should use an XCWorkspace, or at least support using one.
Date Wed, 01 Apr 2015 23:37:54 GMT

    [ https://issues.apache.org/jira/browse/CB-5921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391762#comment-14391762
] 

Shazron Abdullah commented on CB-5921:
--------------------------------------

Actually the web parts of the plugin are not part of the resource bundle. I have a note in
the PoC README that says:
"NOTE: This does not solve copying the plugin's JavaScript into $projectname.xcproject, the
CLI will still have to take care of that, unless we can think of modular alternatives."

The only idea I can think of is the .js is injected into the WebView when the plugin definition
is loaded (from config.xml). For example, in the plugin bundle, there will be a www folder
that contains N number of .js files. 

When all the plugin definitions are read from config.xml, we can begin to load the plugin
.js from each plugin resource's www and inject it in.

Not sure how well this plays with the current way how cordova's plugin js is installed.

> Cordova on iOS should use an XCWorkspace, or at least support using one.
> ------------------------------------------------------------------------
>
>                 Key: CB-5921
>                 URL: https://issues.apache.org/jira/browse/CB-5921
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: iOS
>            Reporter: Graham Mueller
>            Priority: Minor
>              Labels: core
>             Fix For: 4.0.0
>
>         Attachments: build
>
>
> Hi Guys,
> Not sure what to log this as. It's not so much a bug as an incompatibility with other
frameworks. Anyway, this is specifically an issue with the build process on iOS. Do with it
what you will.
> If you're familiar with the CocoaPods framework, you'll know that on initial install,
it creates an XCWorkspace file, and instructs you to exclusively use that afterwards. This
is because the CocoaPods library adds itself as a linked project that must be built, similar
to Cordova/Phonegap. The difference is that Cordova adds itself as a sub project, instead
of a sibling project (which is effectively the workspace goal, from my understanding, though
I'm having a hard time finding a good link to explain it better).
> So, I would suggest that Cordova moves to this setup as well -- it should create the
workspace that has both the Cordova project and your app project.
> Alternatively, if you don't want to go through and change that creation code, it would
be great if the CLI offered someway to specify what you want it to build. I found the actual
build script that's calling xcodebuild with a -project flag in it (this is where -workspace
would go). There is currently no way to override this, so there is currently no way at all
to support workspaces (and consequently no way to use CocoaPods).
> Any thoughts or reasons not to do so?
> Thanks,
> Graham



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org


Mime
View raw message