3 ms·
This is straight from this FAQ: Wayland is a nano display server, relying on drm modesetting, gem batchbuffer submission and hw initialization generally in the
by mahmud 16y ago
This is straight from this FAQ:
Wayland is a nano display server, relying on drm modesetting, gem batchbuffer submission and hw initialization generally in the kernel. Wayland puts the compositing manager and display server in the same process. Window management is largely pushed to the clients, they draw their own decorations and move and resize themselves, typically implemented in a toolkit library.
That last part about integrating the compositing manager and display server into the same process .. that's your main point of departure.
- metageek 16y ago>Window management is largely pushed to the clients, they draw their own decorations and move and resize themselves, typically implemented in a toolkit library. Well, there's a bad idea. I suppose I could see an X replacement which incorporated window management into the server, instead of into a special client; but letting all the clients draw their own borders is a recipe for chaos.
- hencq 16y agoIsn't an X window manager just another X client too at the moment? Couldn't that system still work on Wayland? I might be completely wrong about this though, so someone more knowledgeable please explain. :-)
- metageek 16y agoYes, but it draws the decorations for other clients. The GP said that Wayland clients draw their own decorations.