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

Re: CfC to change Sensor approach, not progress current draft

From: Doug Turner <dougt@mozilla.com>
Date: Thu, 22 Mar 2012 09:36:53 -0700
Cc: Robin Berjon <robin@berjon.com>, Frederick.Hirsch@nokia.com, public-device-apis@w3.org
Message-Id: <DF4CC910-3B53-45FE-9FA1-CF1F5060FAF8@mozilla.com>
To: Dominique Hazael-Massieux <dom@w3.org>

On Mar 22, 2012, at 9:32 AM, Dominique Hazael-Massieux wrote:

> Le jeudi 22 mars 2012 à 09:24 -0700, Doug Turner a écrit :
>> I am taking a much simpler approach to this whole thing.  Here is what
>> I am doing for proximity.  It follows what we did for device motion:
>>    https://dougturner.wordpress.com/2012/03/22/device-proximity/
> 
> It's simpler, but not that much simpler. One reason I took the approach
> I mentioned is that some proximity sensors only report a boolean state
> (near/far); without a notion of accuracy, I don't know how your proposal
> addresses this.

yes, but it is simpler and follows a known pattern. 

> Also, I thought the "activate-on-addEventListener" was considered a bad
> practice based on the feedback to DeviceOrientation?

there is precedent.  we are only sending notifications when there is a change.  that was the objection, iirc. 

Doug
Received on Thursday, 22 March 2012 16:37:26 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:53 UTC