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

Re: [sensors] Device Proximity (was: Device light and proximity sensor)

From: Doug Turner <dougt@mozilla.com>
Date: Tue, 15 May 2012 07:06:45 -0700 (PDT)
To: Anssi Kostiainen <anssi.kostiainen@nokia.com>
Cc: "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>, ext Robin Berjon <robin@berjon.com>
Message-ID: <975507400.912433.1337090805326.JavaMail.root@mozilla.com>
Multiple sensors should be out of scope for v.1.  There are no devices that are shipping or that we know about that are shipping soon that have multiple sensors.  This is the same tradeoff we took for other device specs.


----- Original Message -----
From: "Anssi Kostiainen" <anssi.kostiainen@nokia.com>
To: "ext Robin Berjon" <robin@berjon.com>
Cc: "public-device-apis@w3.org public-device-apis@w3.org" <public-device-apis@w3.org>
Sent: Tuesday, May 15, 2012 12:39:57 AM
Subject: Re: [sensors] Device Proximity (was: Device light and proximity  sensor)


On 10.5.2012, at 1.19, ext Robin Berjon wrote:

> If we're trying to do a generic distance sensor then we're missing at least a field to indicate multiple sensors triggering (which is not common on phones, but I believe is the norm on cars — yes, we have to get used to thinking about those too I'm afraid :).

This reminds me a bit of how multiple touch points are handled in the Touch interface. I added this as an issue to the spec so that it does not go unnoticed.

[I think everyone's fine with me annotating the draft with issues directly instead of using the issue tracker given this in still an unofficial draft. This way we'll surely get more eyeballs on the issues, although it may get a bit ugly.]

Received on Tuesday, 15 May 2012 14:07:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:32:37 UTC