Well if I understand it correctly iOS defines the application version
in a "native" way but not inside the cordova.xml - we want to read this
info from the "native" definition of the app version - right?
Once thing I would like to bring up is the mentioned calls before
deviceready:
I'm not in favor of those since e.g. it is not possible anymore to
deactivate the NetworkStatus plugin in iOS - since it has become a
dependency by issuing commands before it is really used in code - that's
for me a bit dirty since I would like to deactivate all plugins which I
do not need.
So to summarize: I would favor prevent calls of plugins before they are
actually used!
Best,
Viras
Am 2012-05-08 20:07, schrieb Jesse:
Back-stepping a bit ...
Under what circumstances would version 1.0 of the html/js app be
running in
a 2.0 native container ( or vice-versa)? These are the developer's
version
numbers, and identifiers so I am unclear how this is a framework
issue.
Maybe I am confused because all my apps are self aware.
Doesn't this just become a generic data store that is shared between
native/js?
Seems to me if we implemented the widget spec, I could just open the
xml
with XHR and get whatever info I needed ... what am I missing?
On Tue, May 8, 2012 at 10:40 AM, Shazron Abdullah <[email protected]>
wrote:
This was my understanding as well.
On 2012-05-08, at 10:39 AM, Simon MacDonald
<[email protected]>
wrote:
> On Tue, May 8, 2012 at 1:23 PM, Patrick Mueller
<[email protected]>
wrote:
>
>>
>> To clarify a bit, what I was wondering if it was cheap enough to
get
this
>> info during startup and stash it away somewhere in JS, so it'd be
available
>> at deviceready.
>>
>
> This is what I was thinking as well. We'd go get the info an
populate the
> JS object then fire "deviceready". We already use the same
approach when
> setting up Device and Network.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
--
GOFG - Get On Fat Guy
http://www.gofg.at/ - powered by Cordova
