- From: Bryan Sullivan <blsaws@gmail.com>
- Date: Mon, 10 Oct 2011 13:30:30 -0700
- To: JOSE MANUEL CANTERA FONSECA <jmcf@tid.es>
- Cc: "public-device-apis@w3.org" <public-device-apis@w3.org>
Jose, Some comments: In the example, you use "session.startWatch(watchOptions)" when you should be using "sensorConnection". For the "sensor not available" exception, I suggest to use "DOMException.NOT_SUPPORTED_ERR (9)" from http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-17189187. For "threshold", recommend that the description be: The threshold attribute represents a sensor data value which when reached will cause a sensordata event to be delivered. Multiple watch operations with different thresholds can be used for example to monitor sensor "min/max" ranges. Monitoring for a delta changes can also be accomplished by clearing a watch upon the sensordata event, and creating a new watch with the desired delta threshold. No exceptions. I don't see the "SensorManager" interface you refer to re "a proposal to support basic discovery is on the draft under the SensorManager interface.". Thanks, Bryan Sullivan On Sat, Oct 8, 2011 at 3:14 AM, JOSE MANUEL CANTERA FONSECA <jmcf@tid.es> wrote: > > Hi, > A new draft of the sensor API is available at [1]. It tries to capture the different comments received during the last conf. Call and through the mailing list. @Claes a proposal to support basic discovery is on the draft under the SensorManager interface. > Your feedback is needed. > Thanks, all the best > [1] http://dev.w3.org/2009/dap/system-info/Sensors.html > > ________________________________ > Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo. > This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at. > http://www.tid.es/ES/PAGINAS/disclaimer.aspx -- Thanks, Bryan Sullivan
Received on Monday, 10 October 2011 20:31:07 UTC