What It Takes To Write A Wayland Compositor
For those curious about what it takes to write a standalone Wayland compositor and the challenges involved, two Enlightenment developers have shared their struggles and accomplishments in making Enlightenment a Wayland compositor.
As shared a few times now, Enlightenment E19 should be in good shape for Wayland and boasts a huge compositor rewrite. Samsung's Christopher Michael and Stefan Schmidt shared last weekend at FOSDEM about their Wayland experiences.
The FOSDEM 2014 talk focused on Enlightenment as a standalone Wayland compositor and making changes to the rendering, DRM handling, input handling, VT handling, and session recovery to eliminate their dependency on X11. Enlightenment is maintaining their X11 support but have cleaned up their code and made it possible to run Enlightenment and EFL without any dependence on X11/XWayland, but XWayland can still be used with Enlightenment for legacy applications.
In the process of their standalone compositor work they have found some missing pieces to Wayland's current support like the XDG Shell could be better but is admittedly still maturing and there needs to be a protocol extension for session recovery support.
The Enlightenment compositor is right now capable of VT switching, input/output device handling, and running Wayland and X applications. Still being tackled by these developers is buffer abstraction for rendering, session recovery, and other work to make the Enlightenment Wayland compositor suitable for day-to-day work.
Find out more details via the PDF slides.
Latest Articles & Reviews
Latest Linux News
Most Viewed News This Week