On Sun, 2015-04-19 at 15:29 +0900, x414e54 wrote: > > > The way todo this seems to be for the compositor and client to > negotiate an event type they both can understand such as > libinput_event or hid events and then a way to request a revokable > fd to the evdev directly so it can control LEDS and force feedback > etc. This allows for applications and compositors to grow separately > of the wayland protocol so it does not need updating every time > someone invents some new mouse device which needs 128bit integers > instead of doubles, has a z axis, thumbstick or tiny projector built > in, etc. >
There's also the point that nothing stops games or sdl-like layers from using libinput to interpret the evdev stream, there's no need to keep re-implementing device handlers for each client, that way new devices supported by Wayland are automaticaly supported.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel