From 3fd1e128e95770526d2c247aef9544a6abdb7848 Mon Sep 17 00:00:00 2001 From: Kristian Høgsberg Date: Sun, 3 Jun 2012 23:11:34 -0400 Subject: 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. --- TODO | 12 ------------ 1 file changed, 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 -- cgit v1.2.3