On Friday, September 6, 2013, Jesse wrote: > +1 > I would expect the return values to be the same platform ids used by > cordova-cli.[1]
Yes, I believe this is going to be the case. I think it's important that it return the name of the Cordova platform in use, even if that is totally disconnected from the actual device that is running the code. > This would only be a high level value, and if you wanted to know if it was > iPhone or iPad, you would still need to do additional work, but that to me > makes sense as feature detection. Right. If you need to know things about the device itself, then UA detection, feature detection, or even the device plugin are appropriate. > > > On Fri, Sep 6, 2013 at 1:32 PM, Simon MacDonald > <[email protected] <javascript:;>>wrote: > > > +1 I think it is a great idea just don't take it out of device until > > we sit on it for 6 months and forget to tell people we are removing > > it. Not that we'd ever do that. > > Simon Mac Donald > > http://hi.im/simonmacdonald > > > > > > On Fri, Sep 6, 2013 at 3:46 PM, Ian Clelland > > <[email protected]<javascript:;> > > > > wrote: > > > I brought this up on another thread, but I can't find any reference to > > the > > > issue in JIRA, so I'm starting a new thread for visibility. > > > > > > Since cordova-plugin-device was removed from core, and is now an > optional > > > plugin, there is no easy way to determine at runtime what platform an > app > > > is running on. (And yes, feature detection is usually better than > > > user-agent detection, but there are legitimate reasons for switching on > > the > > > *cordova* platform as opposed to any particular feature available in > the > > > webview) > > > > > > I'd like to make this property available as `cordova.platform; it would > > be > > > a simple string taken from the 'id' defined in > > > cordova-js/lib/<platform>/platform.js. > > > > > > Are there any objections to attaching this to the cordova namespace? > > > > > > Ian > > >
