right... I figured rolling this business into a single async api would make sense.
just b/c the w3c hasn't been informed about namespaces doesn't mean we don't have to be! On Tue, May 8, 2012 at 11:18 AM, Shazron <[email protected]> wrote: > This is application version though, not platform? > > On Tue, May 8, 2012 at 2:17 AM, Brian LeRoux <[email protected]> wrote: >> // i'd like something like this... >> require('cordova').platform(function(platform) { >> >> console.log(platform.name) // Tizen <---don't laugh, its gonna happen! >> console.log(platform.version) // '0.7.0' >> >> // gratuitous... >> console.log(platform.version.MAJOR // 7 >> console.log(platform.version.MINOR) // 0 >> console.log(platform.version.PATCH) // 7 >> }) >> >> 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! >>> >>>
