I'm not convinced the device namespace thing is actually helpful for our larger goals at all. Its essentially user agent detection on steroids. Now, ua detection has been vilified even though it was quite useful for polyfilling messed up phones. Given we now have the `./merges` folder I'm less convinced in the utility for that particular use case. Huge benefit of the plugin breakout is that we can maintain a semblance of backwards compatibility, or at least a migration path, while driving the API forward in a more extensible manner.
>From what I understand device.version is needed currently. I'd be happy if we removed the whole thing however unless a compelling use case can be presented. Closer to the browser and faster: win. On Thu, Jun 27, 2013 at 6:16 PM, Andrew Grieve <[email protected]> wrote: > I'd like to see the fields that require an exec() call split out. If they > aren't used, then apps are paying a price on start-up for them. There's > also the fact that some fields require the app to have extra permissions > set in its manifest. > > Suggestion: Leave device.cordova & device.platform in core, but split out > the other fields into a plugin. > > > On Thu, Jun 27, 2013 at 6:25 PM, Joe Bowser <[email protected]> wrote: > >> Agreed. It'd be good to have those features built in. >> >> On Thu, Jun 27, 2013 at 1:56 PM, Shazron <[email protected]> wrote: >> > Makes sense to me. >> > >> > >> > On Thu, Jun 27, 2013 at 1:01 PM, Jesse <[email protected]> wrote: >> > >> >> Looking at the Device API functionality it doesn't make sense to me for >> a >> >> single plugin to define the platform version it was built for. >> >> >> >> We could move this functionality into the framework, but I am reluctant >> to >> >> break APIs if it is not needed. >> >> >> >> I would like to recommend that we leave Device to function as a plugin, >> but >> >> make it an intrinsic plugin. Meaning: >> >> a) the API does not change >> >> b) the device plugin cannot + need not be installed, or uninstalled >> >> c) the device native source code stays in its respective native >> codebase + >> >> repo >> >> d) the device js code stays in cordova-js >> >> >> >> Thoughts? >> >> >> >> Cheers, >> >> Jesse >> >> >> >> @purplecabbage >> >> risingj.com >> >> >>
