- From: Rijubrata Bhaumik via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Sep 2016 15:38:31 +0000
- To: public-device-apis-log@w3.org
@rwaldron : Regarding point 3. A list of available sensors can be easily produced programmatically .. Presence of say AmbientLightSensor in Object.keys(sensors), does not mean the system has a AmbientLightSensor, it means the browser simply has bindings for AmbientLight sensor. We need to make a sync call like start() to find out if the underlying platform actually has a sensor. Also with Android API level 24, there is a concept of dynamic sensor callback which is used for receiving notifications from the SensorManager when dynamic sensors are connected or disconnected. Do you want proposed global object `sensor` object to hold only available sensors for that platform ? Does that mean we need to update the `sensor` object every time a sensor's connection state changes ? I understand the "grouping related classes under a namespace" reasoning, but cannot see benefits beyond that. -- GitHub Notification of comment by riju Please view or discuss this issue at https://github.com/w3c/sensors/issues/127#issuecomment-247364668 using your GitHub account
Received on Thursday, 15 September 2016 15:38:38 UTC