W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2012

Re: Device light and proximity sensor

From: Doug Turner <dougt@mozilla.com>
Date: Wed, 9 May 2012 09:24:21 -0700
Cc: N.V.Balaji <nv.balaji@samsung.com>, "SULLIVAN, BRYAN L" <bs3131@att.com>, Niklas Widell <niklas.widell@ericsson.com>, Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <9E820B3D-EC73-4E0D-B919-4DEFD0226E24@mozilla.com>
To: "Tran, Dzung D" <dzung.d.tran@intel.com>
Yup.

On May 9, 2012, at 9:17 AM, Tran, Dzung D wrote:

> Doug,
> Your suggestion here is to add them as optional to the callback. So are these readonly and constant throughout the events?
>  
> Thanks
> Dzung Tran
>  
> From: Doug Turner [mailto:dougt@mozilla.com] 
> Sent: Wednesday, May 09, 2012 8:29 AM
> To: N.V.Balaji
> Cc: SULLIVAN, BRYAN L; Niklas Widell; Robin Berjon; public-device-apis@w3.org
> Subject: Re: Device light and proximity sensor
>  
>  
> On May 9, 2012, at 8:24 AM, N.V.Balaji wrote:
> 
> 
> I feel, addition of sensor_granularity and interval parameters can help to solve parts of the problems that you have mentioned. The interval parameter is used in device orientation event specification ([1]) as well. Developers can detect the usefulness of the data based on these two parameters.
> 
>  
>  
> :)  Yup.  Lets add both of those (as options) to the spec.
Received on Wednesday, 9 May 2012 16:24:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 16:24:56 GMT