Weston is the reference compositor to Wayland and commonly used for demonstrating new Wayland features and protocol functionality.
Activity Earlier In The Year
- weston: keep non-desktop displays turned off by default
Philipp Zabel: Keep non-desktop heads representing e.g.
- weston-info: add xdg-output support
- compositor-drm: Add drm-backend log debug scope
Daniel Stone: Add a 'drm-debug' scope which prints verbose information about the DRM backend's repaint cycle, including the decision tree on how views are assigned (or not) to planes.
- compositor-drm: Add backend pointer to drm_output
Daniel Stone: Add this for convenience, so it's easier to access when we add the DRM backend debug scope.
- compositor: Add scene-graph debug scope
Daniel Stone: Add a 'scene-graph' debug scope which will dump out the current set of outputs, layers, and views and as much information as possible about how they are rendered and composited.
- compositor: protocol logger
Pekka Paalanen: This is better than running Weston with WAYLAND_DEBUG=server:- It is enabled on demand, no unnecessary flooding and no need to restart the compositor if debug was enabled.
- compositor: add option to enable weston_debug
Pekka Paalanen: Let users enable the compositor debug protocol on the compositor command line.
- libweston: add weston_debug API and implementation
Pekka Paalanen: weston_debug is both a libweston API for relaying debugging messages, and the compositor-debug wayland protocol implementation for accessing those debug messages from a Wayland client.
- man: make substitutions meson-friendly
Pekka Paalanen: Change format of substituted variables to follow the pattern used by configure_file() in Meson.
- README: Move to Markdown, rewrite introduction
Daniel Stone: Move the README file to Markdown, and update it to attempt to explain the current status and use of Weston.
The first sections are user-facing, so they can quickly understand what Weston is, what it does, what it doesn't do, and how to go about using it.