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

Re: [sensors] the near/far event names

From: Doug Turner <dougt@mozilla.com>
Date: Mon, 14 May 2012 07:19:52 -0700 (PDT)
To: Marcos Caceres <w3c@marcosc.com>
Cc: Dzung D Tran <dzung.d.tran@intel.com>, public-device-apis@w3.org, BRYAN L SULLIVAN <bs3131@att.com>
Message-ID: <1508287578.805042.1337005192522.JavaMail.root@mozilla.com>
Use case:

Games -  I want to be able to control some aspect of a game based on the value (not near and far).  For example, I want to control the position of a ball based on how far the user's hand is away from the sensor.



We are going around and around.  There are clearly people asking for both actually values and near/far.  We should support both.




----- Original Message -----
From: "Marcos Caceres" <w3c@marcosc.com>
To: "BRYAN L SULLIVAN" <bs3131@att.com>
Cc: "Dzung D Tran" <dzung.d.tran@intel.com>, public-device-apis@w3.org
Sent: Monday, May 14, 2012 7:03:34 AM
Subject: Re: [sensors] the near/far event names

On 14/05/2012 14:48, SULLIVAN, BRYAN L wrote:
> I was echoing the use case pointed out by Dzung, ie the user is using a laptop, and the very close proximity assumptions of a mobile phone don't apply (unless you wanted to use the proximity sensor to know that a laptop has been closed). In the user proximity case the developer may want to know specifically how far the user is, if such is supported by sensors.
What problem is the developer wanting to solve by knowing the precise 
distance from the user to the device (i.e., in terms of min, max, value 
VS near/far)? With all due respect, the above is not a use case. A use 
case would be something like "If the developer knows that the user is X 
value away, then the developer can do the following things:". No one has 
presented "the following things" yet, specially as they relate to "min, 
max, value" VS "near/far" (apart to working out near/far!).

So, again, can you tell me what you (Bryan) would do with min, max, 
value if you had access to it?
Received on Monday, 14 May 2012 14:20:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 May 2012 14:20:27 GMT