{"id":114477,"date":"2024-03-21T12:25:42","date_gmt":"2024-03-21T10:25:42","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-wayland-protocols-1-34"},"modified":"2026-02-13T12:39:20","modified_gmt":"2026-02-13T10:39:20","slug":"vypusk-wayland-protocols-1-34","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-wayland-protocols-1-34","title":{"rendered":"Release of Wayland-Protocols 1.34","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
After six months of development, the release of the wayland-protocols package 1.34 has been announced, containing a set of protocols and extensions that enhance the capabilities of the basic Wayland protocol and provide the necessary tools for building composite servers and user environments. <\/p>\n
All protocols go through three phases sequentially \u2014 development, testing, and stabilization. Once the development stage (category 'unstable') is finished, the protocol is moved to the 'staging' branch and officially included in the set of wayland-protocols. After testing is complete, it moves to the stable category. Protocols in the 'staging' category can already be used in composite servers and clients where related functionality is required. Unlike the 'unstable' category, changes that break compatibility are prohibited in 'staging', but if issues and shortcomings are identified during testing, replacing it with a new significant version of the protocol or another Wayland extension is not ruled out. <\/p>\n
The new version introduces several new protocols placed in the «staging» category: <\/p>\n
\n
\u00abxdg-toplevel-drag\u00bb \u2014 extends the drag & drop mechanism by enabling the attachment of toplevel windows to a drag operation, which can be used, for example, for organizing dragging toolbars or browser tabs with the mouse. The new protocol allows for creating detachable parts of a window, which, when dragged from this window, become new windows and can move over an existing window before reattaching.\n
\u00abxdg-dialog\u00bb \u2014 allows assigning toplevel surfaces dialog-specific traits, for example, creating modal dialogs that block user interaction with the rest of the interface.\n
'linux-drm-syncobj' \u2014 provides tools for explicit synchronization of buffers using DRM (Direct Rendering Manager) synchronization objects. It is expected that in the context of synchronization during buffer rendering, the proposed protocol will improve interactions with drivers based on graphics APIs Vulkan and OpenGL (implementation relies on handlers in the drivers). The new protocol allows ensuring that the rendering operation to the buffer is completed before the compositor displays this buffer. <\/ul>\n<\/p>\n
Currently, the wayland-protocols package includes the following stable protocols that ensure backward compatibility: <\/p>\n
\n
\"viewporter\" \u2014 allows the client to perform actions for scaling and cropping the edges of a surface on the server side. <\/li>\n
\"presentation-time\" \u2014 ensures video display. <\/li>\n
'xdg-shell' \u2014 an interface for creating and interacting with surfaces as windows, allowing them to be moved across the screen, minimized, maximized, resized, etc.\n
'linux-dmabuf' \u2014 enables the sharing of multiple graphics cards using DMA-BUF technology (allows creating a wl_buffer based on DMA-BUF). <\/li>\n<\/ul>\n
Protocols tested in the «staging» branch: <\/p>\n
\n
drm-lease — provides resources needed to create a stereoscopic image with different buffers for the left and right eyes when outputting to virtual reality headsets. <\/li>\n
«ext-session-lock» — defines means of session locking, such as during a screensaver operation or when displaying an authentication dialog. <\/li>\n
«single-pixel-buffer» — allows the creation of single-pixel buffers that include four 32-bit RGBA values. <\/li>\n
«xdg-activation» — allows focus to be passed between different first-level surfaces (for example, using xdg-activation one application can shift focus to another). <\/li>\n