blob: 429de3020538a8df0f4e06349c8a8c97e614fd43 [file] [log] [blame]
Kristian Høgsberg97f1ebe2008-09-30 09:46:10 -04001
2KEYWORDS:
3
4Wayland is a nano display server, relying on drm modesetting, gem
5batchbuffer submission and hw initialization generally in the
6kernel. Wayland is compositing manager and display server in one
7process. window management is largely pushed to the clients, they
8draw their own decorations and move and resize themselves,
9typically implemented in a library. more of the core desktop could
10be pushed into wayland, for example, stock desktop components such
11as the panel or the desktop background.
12
13It is still designed with a windowed type of desktop in mind, as
14opposed to fullscreen-all-the-time type of interface.
15
Kristian Høgsberg33bea962008-09-30 22:21:49 -040016Current trends goes towards less and less rendering in X server, more
17hardware setup and management in kernel and shared libraries allow
18code sharing without putting it all in a server. freetype,
19fontconfig, cairo all point in this direction, as does direct
20rendering mesa.
Kristian Høgsberg97f1ebe2008-09-30 09:46:10 -040021
22Client allocates DRM buffers, draws decorations, and full window
23contents and posts entire thing to server along with dimensions.
24
25Everything is direct rendered and composited. No cliprects, no
26drawing api/protocl between server and client. No
27pixmaps/windows/drawables, only surfaces (essentially pixmaps). No
28gcs/fonts, no nested windows. OpenGL is already direct rendered,
29pixman may be direct rendered which adds the cairo API, or cairo
30may gain a GL backend.
31
Kristian Høgsberg33bea962008-09-30 22:21:49 -040032Could be a "shell" for launching gdm X server, user session servers,
33safe mode xservers, graphics text console. From gdm, we could also
34launch a rdp session, solid ice sessions.
35
36
Kristian Høgsberg97f1ebe2008-09-30 09:46:10 -040037ISSUES:
38
39Include panel and desktop background in wayland?
40
41How does clients move their surfaces? set a full tri-mesh every time?
42
43How does the server apply transformations to a surface behind the
44clients back? (wobbly, minimize, zoom) Maybe wobble is client side?
45
46How do apps share the glyph cache?
47
48Input handling - keyboard focus, multiple input devices, multiple
49pointers, multi touch.
50
51Drawing cursors, moving them, cursor themes, attaching surfaces to
52cursors. How do you change cursors when you mouse over a text
53field if you don't have subwindows?
54
55synaptics, 3-button emulation, xkb, scim
56
Kristian Høgsberg33bea962008-09-30 22:21:49 -040057changing screen resolution, adding monitors.
58
Kristian Høgsberg97f1ebe2008-09-30 09:46:10 -040059RMI
60
61the get_interface method is called on an object to get an object
62handle that implements the specified interface.