diff options
author | Kristian Høgsberg <krh@redhat.com> | 2009-09-30 23:14:19 -0400 |
---|---|---|
committer | Kristian Høgsberg <krh@redhat.com> | 2009-09-30 23:14:25 -0400 |
commit | beed22b9a39a3f0cb793b986a01f63d4b8695590 (patch) | |
tree | 73869ee16da3be23594a6da5290c2c29d5187c98 /NOTES | |
parent | 12308a49973c54e1524cdbfe4e297759faa3bd74 (diff) | |
download | wayland-beed22b9a39a3f0cb793b986a01f63d4b8695590.tar.gz wayland-beed22b9a39a3f0cb793b986a01f63d4b8695590.tar.xz wayland-beed22b9a39a3f0cb793b986a01f63d4b8695590.zip |
Update TODO
Diffstat (limited to 'NOTES')
-rw-r--r-- | NOTES | 34 |
1 files changed, 0 insertions, 34 deletions
@@ -45,40 +45,6 @@ returned in an event generated by the server once the commit has been executed. This allows clients to throttle themselves against the server and implement smooth animations. - -ISSUES: - -Include panel and desktop background in wayland? - -How does clients move their surfaces? set a full tri-mesh every time? - -How does the server apply transformations to a surface behind the -clients back? (wobbly, minimize, zoom) Maybe wobble is client side? - -How do apps share the glyph cache? - -Input handling - keyboard focus, multiple input devices, multiple -pointers, multi touch. - -Drawing cursors, moving them, cursor themes, attaching surfaces to -cursors. How do you change cursors when you mouse over a text -field if you don't have subwindows? - -synaptics, 3-button emulation, xkb, scim - -changing screen resolution, adding monitors. - -What to do when protocol out buffer fills up? Just block on write -would work I guess. Clients are supposed to throttle using the bread -crumb events, so we shouldn't get into this situation. - -When a surface is the size of the screen and on top, we can set the -scanout buffer to that surface directly. Like compiz unredirect -top-level window feature. Except it won't have any protocol state -side-effects and the client that owns the surface won't know. We lose -control of updates. Should work well for X server root window under -wayland. - Throttling/scheduling - there is currently no mechanism for scheduling clients to prevent greedy clients from spamming the server and starving other clients. On the other hand, now that recompositing is |