Wayland architecture
Sorry for maybe a stupid question, but:
How architecture of Wayland works? Is there anymore a display server or is it just something like a library with hooks?
My understand of the stack is:
the wayland server
(clients)
- Mutter (an windowing manager, a wayland compositor, like an police in the wayland server, writes title bars if clients asks)
- GNOME Shell (just one among other clients, but ask an windowing manager to not add title bars to it and to grant privileges)
- Firefox (ask an windowing manager to add window and title bar)
- Gedit
- ...
or
Mutter (a display server, a wayland compositor, all clients connect to this program to use display)
(clients)
- GNOME Shell (just one among other clients, but ask a display server to not add title bars to it and to grant privileges)
)
- Firefox (ask write window and title bar)
- Gedit
- ...
But then, I found this on Google and it tell Mutter is just a library. Then, maybe stack something like:
GNOME Shell (one binary that contains a display server functions (building this needs libmutter as depency and since libmutter is part of builded binary) and GNOME Shell functions. Mutter exists as a library that is developed separately, but when compiled it is part of GNOME Shell.)
(clients)
- Firefox
- Gedit
- ...
So, how is it? Thank you already :)