You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Shazron <sh...@gmail.com> on 2012/06/12 09:51:26 UTC
iOS - the time has come - we need to have selective compilation of
core plugins (app rejection for inclusion of Contacts API)
See:
https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
iOS still ships with the pre-built .framework binary, so this might
not work even so to remove any core plugins.
I don't think removal from the Cordova.plist will work since I'm
assuming Apple has a class dump tool that checks what frameworks your
.app links to.
Re: iOS - the time has come - we need to have selective compilation
of core plugins (app rejection for inclusion of Contacts API)
Posted by Shazron <sh...@gmail.com>.
Hi Ken,
Currently with iOS we ship a pre-built static lib with all the API
code baked in. This was to overcome Xcode 4 template limitations
(can't define a sub-project, can't define a www folder reference),
which we are removing these limitations by requiring users to create
projects through the command line in 2.0.0.
Since they would require Xcode anyway, there is no dependency, they
just press "Build" and it all should work fine, building the
CordovaLib subproject. This way they will solve the problem by just
removing the Contacts code from the sub-project as they see fit to
satisfy Apple.
Shaz
On Tue, Jun 12, 2012 at 10:44 AM, Ken Wallis <kw...@rim.com> wrote:
> Just to understand, are you referring to compiling platform "native" code as part of this? Just wondering if I am understanding, as this would introduce a bunch of dependencies for the end user?
>
> We had this with WebWorks where you had to have a JDK for BBOS and AIR for PlayBook as our packaging process would build the APIs. We are looking to have prebuilt APIs for BB10, and therefore limit dependency on our Native SDK to those people looking to create custom extensions.
>
> But I probably am not understanding the situation. ;)
> --
>
> Ken Wallis
>
> Product Manager – BlackBerry WebWorks
>
> Research In Motion
>
> (905) 629-4746 x14369
>
> ________________________________________
> From: Shazron [shazron@gmail.com]
> Sent: Tuesday, June 12, 2012 1:36 PM
> To: callback-dev@incubator.apache.org
> Subject: Re: iOS - the time has come - we need to have selective compilation of core plugins (app rejection for inclusion of Contacts API)
>
> Yup - that's why I slated this for 2.0.0 a few weeks ago, but looks
> like we need to push this for 1.9.0
>
> On Tue, Jun 12, 2012 at 10:30 AM, Brian LeRoux <b...@brian.io> wrote:
>> guess its time we stopped shipping the prebuilt and start looking at
>> shipping the src / compile. this will fix our 'permissions for all the
>> things' in android land too
>>
>> On Tue, Jun 12, 2012 at 1:54 AM, Shazron <sh...@gmail.com> wrote:
>>> May or may not be related to this issue:
>>> https://issues.apache.org/jira/browse/CB-902
>>> That's in the future though, but I guess they are preparing now in
>>> existing apps.
>>>
>>> On Tue, Jun 12, 2012 at 12:51 AM, Shazron <sh...@gmail.com> wrote:
>>>> See:
>>>> https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
>>>>
>>>> We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
>>>> iOS still ships with the pre-built .framework binary, so this might
>>>> not work even so to remove any core plugins.
>>>>
>>>> I don't think removal from the Cordova.plist will work since I'm
>>>> assuming Apple has a class dump tool that checks what frameworks your
>>>> .app links to.
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
RE: iOS - the time has come - we need to have selective compilation
of core plugins (app rejection for inclusion of Contacts API)
Posted by Ken Wallis <kw...@rim.com>.
Just to understand, are you referring to compiling platform "native" code as part of this? Just wondering if I am understanding, as this would introduce a bunch of dependencies for the end user?
We had this with WebWorks where you had to have a JDK for BBOS and AIR for PlayBook as our packaging process would build the APIs. We are looking to have prebuilt APIs for BB10, and therefore limit dependency on our Native SDK to those people looking to create custom extensions.
But I probably am not understanding the situation. ;)
--
Ken Wallis
Product Manager – BlackBerry WebWorks
Research In Motion
(905) 629-4746 x14369
________________________________________
From: Shazron [shazron@gmail.com]
Sent: Tuesday, June 12, 2012 1:36 PM
To: callback-dev@incubator.apache.org
Subject: Re: iOS - the time has come - we need to have selective compilation of core plugins (app rejection for inclusion of Contacts API)
Yup - that's why I slated this for 2.0.0 a few weeks ago, but looks
like we need to push this for 1.9.0
On Tue, Jun 12, 2012 at 10:30 AM, Brian LeRoux <b...@brian.io> wrote:
> guess its time we stopped shipping the prebuilt and start looking at
> shipping the src / compile. this will fix our 'permissions for all the
> things' in android land too
>
> On Tue, Jun 12, 2012 at 1:54 AM, Shazron <sh...@gmail.com> wrote:
>> May or may not be related to this issue:
>> https://issues.apache.org/jira/browse/CB-902
>> That's in the future though, but I guess they are preparing now in
>> existing apps.
>>
>> On Tue, Jun 12, 2012 at 12:51 AM, Shazron <sh...@gmail.com> wrote:
>>> See:
>>> https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
>>>
>>> We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
>>> iOS still ships with the pre-built .framework binary, so this might
>>> not work even so to remove any core plugins.
>>>
>>> I don't think removal from the Cordova.plist will work since I'm
>>> assuming Apple has a class dump tool that checks what frameworks your
>>> .app links to.
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Re: iOS - the time has come - we need to have selective compilation
of core plugins (app rejection for inclusion of Contacts API)
Posted by Shazron <sh...@gmail.com>.
Yup - that's why I slated this for 2.0.0 a few weeks ago, but looks
like we need to push this for 1.9.0
On Tue, Jun 12, 2012 at 10:30 AM, Brian LeRoux <b...@brian.io> wrote:
> guess its time we stopped shipping the prebuilt and start looking at
> shipping the src / compile. this will fix our 'permissions for all the
> things' in android land too
>
> On Tue, Jun 12, 2012 at 1:54 AM, Shazron <sh...@gmail.com> wrote:
>> May or may not be related to this issue:
>> https://issues.apache.org/jira/browse/CB-902
>> That's in the future though, but I guess they are preparing now in
>> existing apps.
>>
>> On Tue, Jun 12, 2012 at 12:51 AM, Shazron <sh...@gmail.com> wrote:
>>> See:
>>> https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
>>>
>>> We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
>>> iOS still ships with the pre-built .framework binary, so this might
>>> not work even so to remove any core plugins.
>>>
>>> I don't think removal from the Cordova.plist will work since I'm
>>> assuming Apple has a class dump tool that checks what frameworks your
>>> .app links to.
Re: iOS - the time has come - we need to have selective compilation
of core plugins (app rejection for inclusion of Contacts API)
Posted by Brian LeRoux <b...@brian.io>.
guess its time we stopped shipping the prebuilt and start looking at
shipping the src / compile. this will fix our 'permissions for all the
things' in android land too
On Tue, Jun 12, 2012 at 1:54 AM, Shazron <sh...@gmail.com> wrote:
> May or may not be related to this issue:
> https://issues.apache.org/jira/browse/CB-902
> That's in the future though, but I guess they are preparing now in
> existing apps.
>
> On Tue, Jun 12, 2012 at 12:51 AM, Shazron <sh...@gmail.com> wrote:
>> See:
>> https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
>>
>> We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
>> iOS still ships with the pre-built .framework binary, so this might
>> not work even so to remove any core plugins.
>>
>> I don't think removal from the Cordova.plist will work since I'm
>> assuming Apple has a class dump tool that checks what frameworks your
>> .app links to.
Re: iOS - the time has come - we need to have selective compilation
of core plugins (app rejection for inclusion of Contacts API)
Posted by Shazron <sh...@gmail.com>.
May or may not be related to this issue:
https://issues.apache.org/jira/browse/CB-902
That's in the future though, but I guess they are preparing now in
existing apps.
On Tue, Jun 12, 2012 at 12:51 AM, Shazron <sh...@gmail.com> wrote:
> See:
> https://groups.google.com/d/msg/phonegap/ClZkgVAqhWo/yOn2Be1uVOIJ
>
> We're planning on getting Andrew's plugininstall tool in for 1.9.0 but
> iOS still ships with the pre-built .framework binary, so this might
> not work even so to remove any core plugins.
>
> I don't think removal from the Cordova.plist will work since I'm
> assuming Apple has a class dump tool that checks what frameworks your
> .app links to.