Resurrecting this one.
BlackBerry has the same issue sorta.
I have two play books. One is running 2.0.1.xxx, another 2.1.0.xxx. When I
ask for device.version, I get BlackBerry Playbook OS for both.
Device.name also returns weird stuff for the play books, seem like
arbitrary numbers: 100669958.
Thx duder
On 11/14/12 11:20 AM, Gord Tanner gtan...@gmail.com wrote:
+1 that this is suspect.
I know it just returns what webworks is telling us, we probably need to
read the userAgent or go to native.
Assign the jira to me and I can get this cleaned up for this version.
Sent from my iPhone
I have somewhat similar concern for iOS:
https://issues.apache.org/jira/browse/CB-1837
Wonder whether we should output the model number instead eg iPad2,5
This might solve the comical procedure to detect an iPad Mini (at least for
Cordova):
Yeah. Device.name is an ambiguous-sounding API. Thus my original
recommendation to deprecate device.name and add device.model or
device.hardware.
Basically, this API should return a string that makes it clear what
hardware or model of device it is.
On 11/14/12 11:28 AM, Shazron shaz...@gmail.com
Gord I added https://issues.apache.org/jira/browse/CB-1848
On 11/14/12 11:20 AM, Gord Tanner gtan...@gmail.com wrote:
+1 that this is suspect.
I know it just returns what webworks is telling us, we probably need to
read the userAgent or go to native.
Assign the jira to me and I can get this
I like device.model. Should we adopt it for all the platforms? +1 for me
On Wed, Nov 14, 2012 at 11:44 AM, Filip Maj f...@adobe.com wrote:
Yeah. Device.name is an ambiguous-sounding API. Thus my original
recommendation to deprecate device.name and add device.model or
device.hardware.
Added:
http://issues.cordova.io/1836
http://issues.cordova.io/1837
http://issues.cordova.io/1838
http://issues.cordova.io/1839
http://issues.cordova.io/1840
On Mon, Nov 12, 2012 at 11:14 AM, Shazron shaz...@gmail.com wrote:
Adding jira tasks as per Brian's last comment.
On Thu, Nov 8,
thanks shaz
On Tue, Nov 13, 2012 at 6:39 AM, Shazron shaz...@gmail.com wrote:
Added:
http://issues.cordova.io/1836
http://issues.cordova.io/1837
http://issues.cordova.io/1838
http://issues.cordova.io/1839
http://issues.cordova.io/1840
On Mon, Nov 12, 2012 at 11:14 AM, Shazron
This may get some rotton tomatoes thrown at me but I would be in favor of
axing these apis altogether. I think they are more dangerous than useful /
developers should favor browser feature detection for their UI work.
There is no programmatic reason to want these properties otherwise that I
can
CI implementation is what I am gunning for here (and can actually use it).
I don't like it either but reality is for people building cross-platform
apps at some point you have to do:
if (device.platform == 'android') // do some stuff
For example, knowing when to attach to a back button vs
I like the idea of at least removing this from the start-up path. If users
want to know about the device, they could always call exec() themselves.
On Wed, Nov 7, 2012 at 4:57 PM, Shazron shaz...@gmail.com wrote:
Also, if we remove the device API like Brian suggested, it would be good in
the
11 matches
Mail list logo
