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