Wayland-Protocols has recently published the package Issues Wayland-protocols 1.38 containing a set of protocols and extensions that complement the base protocol Wayland and provide necessary opportunities for building composite servers and user environments.
Protocols within Wayland-Protocols undergo three phases – development, testing, and stabilization. Once the development stage is completed (category “unstable“), the protocol is moved to the “staging” branch and officially included in the set of Wayland-protocols. After testing, protocols are then moved to the stable category. Protocols in the “Staging” category can already be used in composite servers and clients, where their associated functionality is required. Unlike the “Unstable” category, changes that violate compatibility are prohibited in the “Staging” stage.
In the latest version added to the “Staging” category, protocols include:
- xdg-system-bell – allows the display of a system signal that can serve as a warning in terminal emulators, with the signal form determined by the composite manager.
- fifo – implements a first-in-first-out mechanism for processing the updating line of displayed surface contents.
- Commit-timing – allows the restriction of time for the display of surface contents.
In addition to the newly added protocols, Wayland-Protocols includes stable protocols for reverse compatibility:
- “viewPorter” – enables clients to perform scaling and cutting actions on the server side.
- “