diff options
author | Kristian Høgsberg <krh@bitplanet.net> | 2010-11-30 09:27:21 -0500 |
---|---|---|
committer | Kristian Høgsberg <krh@bitplanet.net> | 2010-11-30 09:27:21 -0500 |
commit | f66d28f106a046887d09871b7ba76ddbb9faec92 (patch) | |
tree | 527a8cd74f6f973ed10c306239844704ff3837ee | |
parent | 57a131797c5732002f5997a682973914cce39241 (diff) |
Add window manager faq
-rw-r--r-- | faq.html | 26 |
1 files changed, 25 insertions, 1 deletions
@@ -189,5 +189,29 @@ powerful feature in a protocol. </p> +<h3>How can I replace Wayland's Window Manager?</h3> + +<p> + 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. +</p> + +<p> + 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. +</p> + +<p> +</p> + </body> -</html> +</html> |