Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
The state of Wayland
Posted Apr 10, 2012 16:49 UTC (Tue) by drag (subscriber, #31333)
> How can I replace Wayland's Window Manager?
> The Wayland architecture integrates the display server, window manager and compositor into one process. You can think of Wayland as a toolkit for creating clients and compositors. It is not a specific single compositor or window manager. If you want a different window manager, you can write a new one.
> This may sound like a lot of work, but one of the key points about Wayland is that the boilerplate code to a Wayland compositor is comparable or less than the X boilerplate involved in becoming an X window manager and compositor. Bringing up EGL and GLES2 on the Linux KMS framebuffer and reading input from evdev can be done in less that a thousand lines of code. The Wayland server side library provides the protocol implementation and makes it easy to put the pieces together.
So it seems that it would be perfectly possible to do what the original program did, but it would have to take a entirely different approach.
It seems unlikely that people are going to accept reduced ability to manage windows. So that either means making it possible to script wayland itself or replace the default wayland functionality with something that is scriptable.
Posted Apr 10, 2012 23:54 UTC (Tue) by dgm (subscriber, #49227)
Posted Apr 11, 2012 3:24 UTC (Wed) by scientes (guest, #83068)
Posted Apr 11, 2012 5:21 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)
But it's certainly possible to extend it, the code is simple enough: http://cgit.freedesktop.org/wayland/weston/tree/
Adding a mechanism for custom hooks would be an interesting project.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds