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

RE: Device light and proximity sensor

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Wed, 9 May 2012 16:17:53 +0000
To: Doug Turner <dougt@mozilla.com>, N.V.Balaji <nv.balaji@samsung.com>
CC: "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: <84BCA539DD96614691177EDA3CE4FF0546B1020E@ORSMSX101.amr.corp.intel.com>
Your suggestion here is to add them as optional to the callback. So are these readonly and constant throughout the events?

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:18:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:46:08 UTC