[RFC PATCH v2] protocol: Extend wayland seat with interfaces for sensor inputs.

Lorn Potter lorn.potter at gmail.com
Thu Aug 22 14:43:59 PDT 2013

I was told of this thread, perhaps I can make a few comments (sorry if it doesn't really follow the thread)
[no knowing much about wayland protocol/api]

first thoughts:

* why no timestamp info?
* why no rate info? (not all apps need/want the same speed)
* a magnetometer is not a compass, nor does it describe motion.
  - it seems your 'compass' is really just a magnetometer. A compass entails a sensor fusion of sorts to return heading information in degrees. It uses a magnetometer (calibrated - which mostly means hard and soft iron distortions removed), accelerometer (smoothed for jitter - used for 'leveling' the mag readings), and declination information from somewhere (mostly gps or a location lookup table).
Compass could return magnetic north, true north in degrees from the y axis of the device.

Most importantly, what is the justification for sending sensor data through wayland?

Another thing to consider is you might want to handle axis' rotation when the device is rotated.

Other devices you might consider is like the leapmotion sensor.

Lorn Potter
llornkcor technologies / Jolla Mobile

More information about the wayland-devel mailing list