summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2012-06-03 23:11:34 -0400
committerKristian Høgsberg <krh@bitplanet.net>2012-06-03 23:11:34 -0400
commit3fd1e128e95770526d2c247aef9544a6abdb7848 (patch)
treea22123570333a79f3689582e636107c5c22aa229
parent68f058ffd3aa485e01354b8cf6ad040169e939fb (diff)
TODO: Drop clipboard manager item
We have a reasonable prototype in weston now and we're going to conclude that the persistent selection functionality is either going to be part of the compositor (as for weston) or use a custom protocol.
-rw-r--r--TODO12
1 files changed, 0 insertions, 12 deletions
diff --git a/TODO b/TODO
index 12f22a7..e6f290f 100644
--- a/TODO
+++ b/TODO
@@ -47,18 +47,6 @@ Core wayland protocol
ICCCM
- - clipboard manager interface? what's needed? just notification
- that the selection has gone away. should the clipboard manager be
- able to take over the selection "seamlessly", ie, with the same
- timestamp etc? Doesn't seem like we need that, the clipboard will
- have to set a new data_source anyway, with the subset of mimetypes
- it offers (the clipboad manager may only offer a subset of the
- types offered by the original data_source)
-
- The trouble is that when the clipboard manager sets a new data
- source, we don't want to renew the timestamp and potentially reject
- a newer "real" data source.
-
- mime-type guidelines for data_source (ie, both dnd and selection):
recommended types for text or images, types that a clipboard
manager must support, mime-types must be listed in preferred order