Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of simon.macdonald@gmail.com
 designates 209.85.210.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANpVHHyVT93XG39bK+GqULyZ5vnv56Ac=N7+kxga+MJv72FxeA@mail.gmail.com>
References: 
 <CADVgkyNPjKbXGFcGsZ2Ec=CGUf0GXKvDCdgPsF=Fj+WwdMzxWw@mail.gmail.com>
 <CBCEAFCB.5CFC%fil@adobe.com>
 <CANpVHHyVT93XG39bK+GqULyZ5vnv56Ac=N7+kxga+MJv72FxeA@mail.gmail.com>
From: Simon MacDonald <simon.macdonald@gmail.com>
Date: Fri, 11 May 2012 13:56:30 -0400
Message-ID: 
 <CAM1AYQBPo053zoj-EOPqzNWmeXBPTd6UqAsUiX8mMNdMw9JPyA@mail.gmail.com>
Subject: Re: API addition: application version
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I looked into what Android give you and it seems to be limited to id,
name and version. None of the author information is saved in the .apk
as far as I can tell.

Simon Mac Donald
http://hi.im/simonmacdonald


On Tue, May 8, 2012 at 3:46 PM, Anis KADRI <anis.kadri@gmail.com> wrote:
> 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 <fil@adobe.com> 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" <b@brian.io> 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 <michael@michaelbrooks.ca>
>> >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 <shazron@gmail.com>
>> >>wrote:
>> >>
>> >>> This was my understanding as well.
>> >>>
>> >>> On 2012-05-08, at 10:39 AM, Simon MacDonald <simon.macdonald@gmail.com
>> >
>> >>> wrote:
>> >>>
>> >>> > On Tue, May 8, 2012 at 1:23 PM, Patrick Mueller <pmuellr@gmail.com>
>> >>> 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
>> >>>
>>
>>