

And finally, a change that is not visible in the API, but should make our lives easier as developers: We have streamlined the implementation and Qt Wayland now follows the standard Qt PIMPL( Q_DECLARE_PRIVATE) pattern.

#WAYLAND COMPOSITOR PATCH#
We will keep source and binary compatibility for all the 5.7.x patch releases, but since this is a tech preview, we will be adding non-compatible improvements to the API before the final release. Here’s a snapshot of a demo that we showed at Embedded World: it is a compositor containing a launcher and a tiling window manager, written purely in QML. Now we have rewritten the API, making it more powerful and much easier to use. Qt Wayland has included a compositor API since the beginning, but this API has never been officially released.
#WAYLAND COMPOSITOR HOW TO#
You can precisely control how to display information from the other processes, and also add your own GUI elements. The compositor API allows you to create a truly custom UI for the display server. Wayland support in Qt makes it possible to split your UI into different processes, increasing robustness and reliability. It is particularly relevant for embedded and mobile systems. Wayland is a light-weight display server protocol, designed to replace the X Window System. In this post, I'll give you an overview of the functionality along with few examples on how to create your own compositors with it. As part of the forthcoming Qt 5.7, we are happy to be releasing a tech preview of the new Qt Wayland Compositor API.
