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

[Stefan Schmidt]

Hello.

Sorry for the delay. Got sick in between.
Thanks for taking the time to review this.

On 08/12/2013 05:14 PM, Thomas Daede wrote:
> On Thu, Aug 1, 2013 at 3:39 AM, Stefan Schmidt <s.schmidt at samsung.com>
> wrote:
>
>> +    <event name="motion">
>> +      <description summary="Motion event coming from the compass
> sensor">
>> +       Updated sensor data available from compass
>> +      </description>
>> +      <arg name="x" type="fixed" summary="x-axis"/>
>> +      <arg name="y" type="fixed" summary="y-axis"/>
>> +      <arg name="z" type="fixed" summary="z-axis"/>
>> +    </event>
>
> These events don't have any units, and there isn't any particular
> information about the sensor passed either. Is this supposed to be
> read out of band? Presuming the motion integration happens in the
> client. it's very important for a coordinate system to be defined
> between the accelerometer, gyroscope, and compass, and information
> like sensor bandwidth is also important.

I added units as well as a coordinate system description now. Please see 
the attachment for the current version and let me know if that covers 
it. Going to send it out next week and would be happy about more 
feedback. :)

> Sensors that combine all three of the above with an integral IMU
> processor are also becoming more and more common - that's at least one
> more type that we will need. I definitely think the interface should
> be designed - the abstraction has to be somewhere, and I'd prefer it

Did you miss to finish the sentence? My parser fails on it. :)

> here rather than every client accessing the devices directly - but I
> want to make sure that this is possible with all sorts of devices in
> the future.

What exactly are you missing? I started small here on purpose. But based 
on some real needs this can be extended. Nothing set in stone.

> There a number of other devices that I'd like to see implemented in
> this manner - for example, 3D mice. In this case, unlike the motion
> sensors, window focus does matter.

What would you propose to handle these?

regards
Stefan Schmidt

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-protocol-Extend-wayland-seat-with-interfaces-for-sen.patch
Type: text/x-patch
Size: 7292 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20130816/41806dcf/attachment.bin>