Update TODO

NOTES

@@ -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