So why do we need a new API?Ĭomparing to the existing interfaces, Generic Sensor API provides a great number of advantages: You might think that the web platform already provides sensor data and you are absolutely right! For instance, DeviceMotion and DeviceOrientation events expose motion sensor data. For example, the AbsoluteOrientation sensor provides a ready-to-use four-by-four rotation matrix based on the data obtained from the accelerometer, gyroscope, and magnetometer.
Other sensors, referred to as fusion sensors, merge data from several low level sensors to expose information a script would otherwise need to calculate. These are referred to as low-level sensors. Some sensor classes interface to actual hardware sensors such as, for example, the accelerometer or gyroscope classes. It is super tiny! The core functionality is specified by the base interface, and Gyroscope merely extends it with three attributes representing angular velocity. For instance, take a look at the Gyroscope class. Having a base interface simplifies the implementation and specification process for the concrete sensor classes. The API consists of the base Sensor interface and a set of concrete sensor classes built on top. The Generic Sensor API is a set of interfaces which expose sensor devices to the web platform. Wouldn't it be cool to bridge the gap between platform-specific and web applications? Enter the Generic Sensor API, for the web! What is the Generic Sensor API? # Today, sensor data is used in many platform-specific applications to enable use cases such as immersive gaming, fitness tracking, and augmented or virtual reality. Sensor readings delivery can be suspended.Debugging and sensor overriding with Chrome DevTools.Synchronization with screen coordinates.
0 kommentar(er)
