RE: [sensors] the near/far event names

Thanks, Dzung. For the PC/laptop use case it does make more sense for the API to provide an actual number. I was not thinking of that use case.

Thanks,
Bryan Sullivan 

-----Original Message-----
From: Tran, Dzung D [mailto:dzung.d.tran@intel.com] 
Sent: Sunday, May 13, 2012 4:48 PM
To: SULLIVAN, BRYAN L; Marcos Caceres
Cc: public-device-apis@w3.org
Subject: RE: [sensors] the near/far event names

Just a couple of notes:

- You probably don't want the near/far to be part of the same event as value,min,max since the near/far event will be fired less frequent than value,min,max event.

- Near for phone will be different than near for notebook/laptop/all-in-one. Near for phone is right up to your face when near for notebook/laptop/all-in-one would be 1-2 ft.

Thanks
Dzung Tran

-----Original Message-----
From: SULLIVAN, BRYAN L [mailto:bs3131@att.com] 
Sent: Sunday, May 13, 2012 2:23 PM
To: Marcos Caceres
Cc: public-device-apis@w3.org
Subject: Re: [sensors] the near/far event names

Ok, I will think it over. Maybe in this case just a "close / not close" event will suffice, if we can get implementations to use the same meaning for these (e.g. 2cm, with an event fired when it passes in the respective getting closer or moving away direction).

Thanks,
Bryan Sullivan

On May 13, 2012, at 11:49 AM, "Marcos Caceres" <marcosscaceres@gmail.com> wrote:

> Hi Bryan, 
> 
> On Sunday, 13 May 2012 at 09:32, SULLIVAN, BRYAN L wrote:
> 
>> Similar to ambient sound and light, we need real/meaningful numbers for this API. 
> 
> What use cases do you foresee, or have in mind, for these numbers?  
>

Received on Monday, 14 May 2012 03:40:17 UTC