mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2026-02-15 22:05:35 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
Core Wayland window system code and protocol
2524 commits 25 branches 109 tags 26 MiB
Find a file
Pekka Paalanen e127c29d10 protocol: change wl_surface.enter/leave wording 
The existing wording has been carried from the introduction of the enter
and leave events in

commit a5df3de101
Date:   Tue Apr 17 17:22:45 2012 -0400

    Add wl_surface.enter and wl_surface.leave events

However, the modern understanding is that a surface cannot enter an
output unless it would actually be shown there, at least if no other
surfaces existed in the compositor. For a surface to be shown, it must
mapped, and it cannot be mapped without contents and a role. A
wl_surface is created without contents and without a role, so simply
creating a wl_surface cannot result in enter events.

The enter and leave events have traditionally been used to infer the
output scale and tranform that would be best for the client to use. This
is indirect, somewhat vague, and does not work for a surface's initial
drawing, which is why the wl_surface events preferred_buffer_scale and
preferred_buffer_transform were introduced. This removes any remaining
doubt that enter could be triggered simply by creating a wl_surface.

Therefore, let's fix the wording here.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com>
2023-09-18 12:02:19 +03:00
.gitlab/issue_templates Add a basic gitlab issue template 2020-08-18 07:57:26 +00:00
cursor cursor: check return value of snprintf() 2023-08-02 16:47:07 +02:00
doc Document which type are nullable, and wire format for null value 2022-07-14 08:38:49 -07:00
egl egl: add missing ABI check test 2023-06-20 09:20:49 +02:00
protocol protocol: change wl_surface.enter/leave wording 2023-09-18 12:02:19 +03:00
src client: Add method to get display for a given proxy 2023-08-07 13:38:01 +00:00
tests client: Add method to get display for a given proxy 2023-08-07 13:38:01 +00:00
.editorconfig editorconfig: add settings for the .gitlab-ci.yml file 2020-06-05 08:22:34 +10:00
.gitignore build: drop autotools 2021-03-05 09:15:04 +00:00
.gitlab-ci.yml ci: upgrade FreeBSD to 13.2 2023-08-02 16:47:07 +02:00
.mailmap Add a .mailmap file 2023-03-25 11:17:32 -05:00
.triage-policies.yml Add a triage-policies file for bugbot 2023-07-07 21:18:08 +10:00
CONTRIBUTING.md CONTRIBUTING: fix typo "excercising" 2020-12-17 16:03:14 -05:00
COPYING COPYING: Update to MIT Expat License rather than MIT X License 2015-06-12 15:31:21 -07:00
meson.build build: re-open main branch for regular development 2023-04-04 13:38:18 +02:00
meson_options.txt meson: Use proper type for bools 2022-04-02 17:04:08 +03:00
README.md readme: convert to Markdown 2023-02-13 19:57:15 +01:00
release.sh release.sh: Don't push *all* tags 2023-01-16 10:03:54 +00:00
releasing.txt Add release.sh 2022-07-14 08:04:43 +00:00
wayland-scanner.m4 build: check wayland-scanner version 2020-01-16 17:25:06 +01:00
wayland-scanner.mk Pass input/output files as arguments to wayland-scanner 2017-08-18 15:20:24 +03:00

README.md

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.