Difference between revisions of "Wayland"
Jump to navigation
Jump to search
Line 13: | Line 13: | ||
* https://wiki.archlinux.org/index.php/Wayland | * https://wiki.archlinux.org/index.php/Wayland | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Line 32: | Line 22: | ||
* Drew DeVault’s Blog: [https://drewdevault.com/2017/10/09/Future-of-sway.html The future of Wayland, and sway’s role in it] | * Drew DeVault’s Blog: [https://drewdevault.com/2017/10/09/Future-of-sway.html The future of Wayland, and sway’s role in it] | ||
− | |||
− | |||
* [https://drewdevault.com/2019/02/10/Wayland-misconceptions-debunked.html Wayland misconceptions debunked] | * [https://drewdevault.com/2019/02/10/Wayland-misconceptions-debunked.html Wayland misconceptions debunked] | ||
Line 45: | Line 33: | ||
− | |||
− | |||
− | * | + | * https://github.com/MirServer/wlcs - Wayland Conformance Test Suite |
− | + | ||
− | + | ||
+ | == Libraries == | ||
+ | === wlroots === | ||
+ | * https://github.com/swaywm/wlroots - A modular Wayland compositor library | ||
+ | * [https://drewdevault.com/2018/07/17/Input-handling-in-wlroots.html Input handling in wlroots] | ||
− | * [https://drewdevault.com// | + | * [https://drewdevault.com/2018/07/29/Wayland-shells.html Writing a Wayland compositor with wlroots: shells] |
− | * https://github.com/ | + | === smithay === |
+ | * https://github.com/Smithay/smithay - aims to provide building blocks to create wayland compositors in Rust. While not being a full-blown compositor, it'll provide objects and interfaces implementing common functionnalities that pretty much any compositor will need, in a generic fashion. | ||
== Compositors == | == Compositors == |
Revision as of 21:21, 6 May 2019
General
- Wayland is intended as a simpler replacement for X, easier to develop and maintain. GNOME and KDE are expected to be ported to it. Wayland is a protocol for a compositor to talk to its clients as well as a C library implementation of that 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.
Part of the Wayland project is also the Weston reference implementation of a Wayland compositor. Weston can run as an X client or under Linux KMS and ships with a few demo clients. The Weston compositor is a minimal and fast compositor and is suitable for many embedded and mobile use cases.
- WP: Wayland_(display_server_protocol) - a computer protocol that specifies the communication between a display server and its clients, as well as a reference implementation of the protocol in the C programming language.[8] A display server using the Wayland protocol is called a Wayland compositor.Wayland is developed by a group of volunteers initially led by Kristian Høgsberg as a free and open community-driven project with the aim of replacing the X Window System with a modern, simpler windowing system in Linux and other Unix-like operating systems.[8] The project's source code is published under the terms of the MIT License, a permissive free software licence
- Drew DeVault’s Blog: The future of Wayland, and sway’s role in it
- https://github.com/MirServer/wlcs - Wayland Conformance Test Suite
Libraries
wlroots
- https://github.com/swaywm/wlroots - A modular Wayland compositor library
smithay
- https://github.com/Smithay/smithay - aims to provide building blocks to create wayland compositors in Rust. While not being a full-blown compositor, it'll provide objects and interfaces implementing common functionnalities that pretty much any compositor will need, in a generic fashion.
Compositors
sway
- Sway - tiling Wayland compositor and a drop-in replacement for the i3 window manager for X11. It works with your existing i3 configuration and supports most of i3's features, plus a few extras.
way-cooler
adwc
- https://github.com/detomastah/adwc - adwm clone, dead
wayfire
Screenshots
- https://github.com/emersion/grim - Grab images from a Wayland compositor
- https://github.com/emersion/slurp - Select a region in a Wayland compositor and print it to the standard output.