I'll just go ahead and create the tasks for device.model (and
device.namedeprecation) - if there's a reason not to, please chime in.
http://issues.cordova.io/1850
On Wed, Nov 14, 2012 at 12:00 PM, Shazron wrote:
> I like device.model. Should we adopt it for all the platforms? +1 for me
>
>
> O
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 wrote:
> 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
Gord I added https://issues.apache.org/jira/browse/CB-1848
On 11/14/12 11:20 AM, "Gord Tanner" 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 f
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" wrote:
>I have
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):
http://stackoverflow.com/questions/13248493/detect-ipad-m
Thx duder
On 11/14/12 11:20 AM, "Gord Tanner" 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
>
>On 201
+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
On 2012-11-14, at 2:14 PM, Filip Maj wrote:
> Resurrecting this one.
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: 10066995
thanks shaz
On Tue, Nov 13, 2012 at 6:39 AM, Shazron 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 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 wrote:
> Adding jira tasks as per Brian's last comment.
>
>
> On Thu, Nov 8, 2012 at 9:52 AM,
Adding jira tasks as per Brian's last comment.
On Thu, Nov 8, 2012 at 9:52 AM, Shazron wrote:
> +1 sounds like a plan
>
>
> On Thu, Nov 8, 2012 at 9:34 AM, Filip Maj wrote:
>
>> +1
>>
>> On 11/8/12 4:01 AM, "Brian LeRoux" wrote:
>>
>> >I think would it make sense to:
>> >
>> >1. align apis as
+1 sounds like a plan
On Thu, Nov 8, 2012 at 9:34 AM, Filip Maj wrote:
> +1
>
> On 11/8/12 4:01 AM, "Brian LeRoux" wrote:
>
> >I think would it make sense to:
> >
> >1. align apis as orig msg from fil suggests
> >2. drop in deprecation notice for sync usage and add to deprec page
> >3. add asy
+1
On 11/8/12 4:01 AM, "Brian LeRoux" wrote:
>I think would it make sense to:
>
>1. align apis as orig msg from fil suggests
>2. drop in deprecation notice for sync usage and add to deprec page
>3. add async equiv and get it out of startup path as andrew suggests
>
>
>
>
>On Wed, Nov 7, 2012 at
I think would it make sense to:
1. align apis as orig msg from fil suggests
2. drop in deprecation notice for sync usage and add to deprec page
3. add async equiv and get it out of startup path as andrew suggests
On Wed, Nov 7, 2012 at 7:13 PM, Filip Maj wrote:
> Although I think we're close
Although I think we're close to being able to author cross-platform apps
sans UA detection , I think people still have valid use cases to use it.
On 11/7/12 6:18 PM, "Andrew Grieve" wrote:
>I like the idea of at least removing this from the start-up path. If users
>want to know about the device,
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 wrote:
> Also, if we remove the device API like Brian suggested, it would be good in
> the sense that we wo
Also, if we remove the device API like Brian suggested, it would be good in
the sense that we won't have to call the CDVDevice plugin to populate some
js variables before deviceready can fire -- eliminating a dependency.
On Wed, Nov 7, 2012 at 11:00 AM, Shazron wrote:
> Agree with Fil to make i
Agree with Fil to make it consistent - in essence this is an iOS bug :)
Brian, there is one case I can think of -- detecting the iPad mini's
features using js - Max Firt investigated trying to do it
http://www.mobilexweb.com/blog/ipad-mini-detection-for-html5-user-agent but
the only kludgy way rig
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 render
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 th
Currently if you ask for device.platform you will get several different
responses on iOS. You'll get iPhone, iPad, iPod Touch, etc. This seems
backwards. IMO all of these should return 'iOS'.
Related, device.name returns the custom device name as the user defines it
in iTunes. IMO it should return
21 matches
Mail list logo
