mirrors
/
weston
mirror of https://gitlab.freedesktop.org/wayland/weston.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Delete a few duplicate TODO items

This commit is contained in:
Kristian Høgsberg 2010-07-29 00:02:58 -04:00
parent 43788b13df
commit eba6f0d32b
1 changed files with 3 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
TODO
View File

@ -1,6 +1,6 @@
Core wayland protocol Core wayland protocol
- implement glyph cache and dnd - glyph cache
- dnd, figure out large object transfer: through wayland protocol or - dnd, figure out large object transfer: through wayland protocol or
pass an fd through the compositor to the other client and let them pass an fd through the compositor to the other client and let them
@ -29,14 +29,6 @@ Core wayland protocol
switching away from. for minimized windows that we don't want live switching away from. for minimized windows that we don't want live
thumb nails for. etc. thumb nails for. etc.
- Move/resize protocols? In the style of the dnd protocol, if a
surface has grabbed an input, it can request a resize (top/bottom |
left/right) or a move. Goes on for duration of grab or until
surface cancels. Surface gets resize(w,h) during resize events and
must reallocate buffer and redraw.
- Initial surface placement issue.
- Consolidate drm buffer upload with a create_buffer request, returns - Consolidate drm buffer upload with a create_buffer request, returns
buffer object we can use in surface.attach, cache.upload and buffer object we can use in surface.attach, cache.upload and
input.attach? Will increase object id usage significantly, each input.attach? Will increase object id usage significantly, each
@ -95,6 +87,8 @@ Core wayland protocol
- multi touch? - multi touch?
- synaptics, 3-button emulation, scim
- sparse/gcc plugin based idl compiler - sparse/gcc plugin based idl compiler
- crack? - crack?
@ -131,12 +125,6 @@ Core wayland protocol
- multi gpu, needs queue and seqno to wait on in requests - multi gpu, needs queue and seqno to wait on in requests
- synaptics, 3-button emulation, scim
- 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.
Clients and ports Clients and ports
- port gtk+ - port gtk+