Bada gives access to application details (app name, version, etc...) so once we decided what api to use, I can start working on it. Are we doing that widget spec for sure ?
On Tue, May 8, 2012 at 11:11 AM, Filip Maj <[email protected]> wrote: > Inside the www, just like BB WebWorks / PhoneGap Build apps, all based on > the w3c spec. > > On 5/8/12 10:58 AM, "Brian LeRoux" <[email protected]> wrote: > > >ok cool, eh so where does config.xml live in an android proj anyhow? > >or any platform for that matter? inside the www? > > > >(happy we are officially going to start supporting it. still think we > >should re-think the device object and the baggage it contains into > >something else.) > > > >should this be something we gun for 1.9 ??? > > > >On Tue, May 8, 2012 at 7:46 PM, Michael Brooks <[email protected]> > >wrote: > >> My understanding as well. Before deviceready, read the config.xml and > >> populate some variables. We're talking about the application metadata, > >>not > >> the device's information. > >> > >> On Tue, May 8, 2012 at 1:40 PM, 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 > >>> > >
