kb/linux
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

modified: README.md

Browse Source 
modified:   docs/desktop-environments/kde.md
renamed:    docs/desktop-environments/xfc4.md -> docs/desktop-environments/xfce4.md
new file:   docs/display-managers/gdm.md
new file:   docs/display-managers/sddm.md
new file:   docs/display-protocols/wayland.md
new file:   docs/display-protocols/x11.md
new file:   docs/window-managers/hyprland.md
new file:   docs/window-managers/kwin.md
This commit is contained in:
Márcio Fernandes
2025-11-01 09:20:54 +00:00
parent 6acd7c0a1f
commit 170a97819b
9 changed files with 160 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/display-protocols/wayland.md Normal file
View File

@@ -0,0 +1,16 @@
# Wayland
Wayland is a modern display protocol and architecture that replaces the aging X11 system on Linux. It defines how applications communicate with the display server to render graphics and handle input.
**🧩 Core Concepts of Wayland:**
Protocol, not a server: Wayland is a specification — it defines how clients (apps) and the compositor (display server) talk to each other.
Compositor = Display Server + Window Manager: In Wayland, the compositor handles both rendering and window management. Examples include:
- [Mutter (GNOME)](../desktop-environments/gnome.md)
- [KWin (KDE Plasma)](../window-managers/kwin.md)
- [Hyprland](../window-managers/hyprland.md), Sway, river, etc.
Direct rendering: Applications render their own graphics and hand them off to the compositor, reducing complexity and improving performance.