3 ms·
>> In an ideal world there would be a nice clean abstraction boundary between compositor and DE so that this underlying work was shared between DEs. Not sure w
by phkahler 3y ago
>> In an ideal world there would be a nice clean abstraction boundary between compositor and DE so that this underlying work was shared between DEs.
Not sure what's ideal about that. With Wayland the DE IS the compositor. There are a lot of benefits to that. I would hope basic compositing is a fairly small amount of code and many DEs could build on that - which I guess would your clean boundary even if it's in the same process.
- rkangel 3y agoI think my point is that wlroots is a set of building blocks, rather than a single library. You can't build an unopinionated single library that just takes care of the Waylandness of your DE, that you can build on top of. The compositing and the windowing and the event handling are all intertwined, so instead the best you can do is wlroots which gives you some blocks you can put together in the appropriate way. It makes for complex, significant work for any Wayland DE, with less shared work. I don't think this is wrong - it seems this is the approach we need to get full featured DEs, it's just unfortunate that that's how reality has worked out.