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 07:46:07 -0700
Cc: Niklas Widell <niklas.widell@ericsson.com>, Robin Berjon <robin@berjon.com>, "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Message-Id: <53CEA83A-03E9-4FA3-A534-751193906A84@mozilla.com>
To: "SULLIVAN, BRYAN L" <bs3131@att.com>

On May 9, 2012, at 7:40 AM, SULLIVAN, BRYAN L wrote:

> On the DAP call today I mentioned some thing related to this, and Dzung's update to the Sensor spec in response to Doug's spec. Overall, my goal is that we get specs to CR with at least the minimum functionality that developers need to build effective apps. The one/many spec debate has been had before, and I will remain on the sideline there (ere are valid points on both sides).

Agreed.

> I'm more concerned that the Sensor APIs contain the essential functionality. I'm not yet convinced that a simple min/max response for the ambient sound/light and proximity sensors will be enough, ie that no information/control of trigger points and event rate is needed. But I can be convinced if someone can explain how a Web developer would deal with such issues in an efficient, cross-platform way in the case that platforms vary widely in these additional aspects.

Turn this around Bryan.  Explain why you think that trigger points or an event rate is needed.  Show, with an example for bonus points :) , how an application would be that much better if such apis exists.  My claim is you don't -- you have minimum functionality to build effective apps.

Doug
Received on Wednesday, 9 May 2012 14:46:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 14:46:41 GMT