3 ms·

> it's not terribly complicated to pass exclusive access to display across processes. You're just starting to re-invent the Wayland protocol. You need to pass

> it's not terribly complicated to pass exclusive access to display across processes. You're just starting to re-invent the Wayland protocol. You need to pass input too… and more of Wayland re-invented. >desktop environments are huge Weston or Cage doesn't really qualify as huge. Also, I think you underestimate the work to write a program using KMS and libinput. It's pretty easy to write a toy app, but writing a solid framework is something else.

Const-me 6y ago
> You're just starting to re-invent the Wayland protocol I think the main feature of WL is simultaneous multi-tasking. If you don't need that, a desktop is redundant. That's why Google made their own proprietary DM for android instead of adapting what Linux had. > You need to pass input too I haven't tried but I think multiple processes are fine reading from the same /dev/input/event[n] at the same time, they'll just get the same events. Therefore they may process or ignore these based on whether they rendering or not. > I think you underestimate the work to write a program using KMS and libinput I did it several times, both for hire and for lulz: https://github.com/Const-me/Vrmac/ https://github.com/Const-me/Vrmac/ drm/kms pieces are in C++ and not in that repo, but raw input is there, was easy: https://github.com/Const-me/Vrmac/tree/master/Vrmac/Input/Linux https://github.com/Const-me/Vrmac/tree/master/Vrmac/Input/Li... > writing a solid framework is something else Depends on the scope. If you only need left to right languages, couple keyboard layouts out of the 204, etc., it's reasonable.