33be03451a
Originally, having the drag source client in charge of cursor updates was simple enough, flexible and coherent with the prior art. Things accumulated over time that made it not such a great choice: - The tablet protocol sporting its own on-screen pointer cursors made clients need to be painfully aware of the device that started drag-and-drop, in order to modify the correct cursor, provide the correct serials, etc. - The shapes protocol greatly simplified the set of sensible cursors - On top of that, not every compositor nor toolkit library knows to do well all of that. Nowadays, it seems simpler to leave this bit of user feedback up to the compositor, as it will/should be aware of the device driving drag-and-drop, as well as the currently selected action. In order to allow for a seamless transition (mostly in the client side), document this as mandatory only if version 4 of the wl_data_* interfaces is implemented by the compositor. The version bump only identifies to clients the possibility to avoid doing any cursor feedback themselves. Signed-off-by: Carlos Garnacho <carlosg@gnome.org> |
||
|---|---|---|
| .gitlab/issue_templates | ||
| cursor | ||
| doc | ||
| egl | ||
| protocol | ||
| src | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .mailmap | ||
| .triage-policies.yml | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| meson.build | ||
| meson_options.txt | ||
| README.md | ||
| release.sh | ||
| releasing.txt | ||
| wayland-scanner.m4 | ||
| wayland-scanner.mk | ||
Wayland
Wayland is a project to define a protocol for a compositor to talk to its clients as well as a library implementation of the protocol. The compositor can be a standalone display server running on Linux kernel modesetting and evdev input devices, an X application, or a wayland client itself. The clients can be traditional applications, X servers (rootless or fullscreen) or other display servers.
The wayland protocol is essentially only about input handling and buffer management. The compositor receives input events and forwards them to the relevant client. The clients creates buffers and renders into them and notifies the compositor when it needs to redraw. The protocol also handles drag and drop, selections, window management and other interactions that must go through the compositor. However, the protocol does not handle rendering, which is one of the features that makes wayland so simple. All clients are expected to handle rendering themselves, typically through cairo or OpenGL.
Building the wayland libraries is fairly simple, aside from libffi, they don't have many dependencies:
$ git clone https://gitlab.freedesktop.org/wayland/wayland
$ cd wayland
$ meson build/ --prefix=PREFIX
$ ninja -C build/ install
where PREFIX is where you want to install the libraries.
See https://wayland.freedesktop.org for documentation.