The AGL Wayland Compositor, Present and Future Design Work
summary
AGL uses a libWeston-based Wayland compositor that owns outputs, inputs and stacking and migrates private wl extensions (wl_shell, AGL shell desktop) into a gRPC-based window-management API so clients can request activation, receive continuous window state events, and avoid direct Wayland wiring. A gRPC proxy helper runs alongside the compositor to implement the shell protocol; Chromium and Flutter lack reliable multi-top-level-surface support so the team implements a designated-activation-rectangle workaround (demoed for Flutter) instead of costly per-surface engines.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:41Outline and agenda
- 6:53Private extensions - can we do better?
- 8:08Window management with gRPC
- 14:45More than one ecosystem
- 15:43Qt ecosystem
- 16:49WAM/chromium ecosystem
- 18:14Flutter ecosystem
- 21:28Flutter & Chromium runtime
- 22:14Flutter & WAM/chromium runtime
related talks
10mLightning Talk: The AGL Wayland Compositor
23mWayland Goal Status Update
51mWayland and Weston: 8 years of production devices
30mHello Wayland, Goodbye X11 - The year of the Linux desktop!
32mThe Modern Linux Graphics Stack on Embedded Systems
19mStatus of Chromium Embedded Framework (CEF) and Webapps on AGL
32mAchieving a Software-Defined Multi-Display System with Unified HMI
05mBuilding Graphical Appliances Made Easy