+1 window.widget On 5/7/12 7:58 PM, "Michael Brooks" <[email protected]> wrote:
>Could we consider using the W3C Widget Interface [1]? It's a programmatic >interface to the W3C Widget Specification [2]. > >In that case, it would be: window.widget.version > >[1] http://www.w3.org/TR/widgets-apis/#the-widget-interface >[2] http://www.w3.org/TR/widgets/ > >On Mon, May 7, 2012 at 10:53 PM, Shazron <[email protected]> wrote: > >> I like navigator.app.version >> >> On Mon, May 7, 2012 at 7:50 PM, Simon MacDonald >> <[email protected]> wrote: >> > Seems easy to do on android and probably belongs in >>navigator.app.version >> > since app is our own non-W3C extension. >> > >> > Simon >> > >> > On Monday, May 7, 2012, Filip Maj wrote: >> > >> >> Stems from https://issues.apache.org/jira/browse/CB-635 >> >> >> >> TL;DR: providing a JS API in cordova for accessing the application >> version >> >> as defined in native. Shaz has already commented on how to do this in >> iOS. >> >> In Android I understand the manifest versionCode / versionString >> >> properties are available (and should be accessible). >> >> >> >> First question: is this a valuable API? IMO: yes. Programmatically >> >> accessing app version for issue resolution and stuff like that seems >> like >> >> a good thing. >> >> >> >> Second question: How viable is this for Bada / WP7 / BB WebWorks / >>other >> >> platforms? >> >> >> >> Third question (assuming Q1 response is "yes"): how to frame this >>API? >> >> >> >> Thoughts/comments/suggestions appreciated! >> >> >> >> >> > >> > -- >> > Simon Mac Donald >> > http://hi.im/simonmacdonald >>
