Just to clarify what's going on with cut/copy/paste/duplicate for items...
- Currently, "Copy" puts the UUID of the item on the clipboard
- "Paste" takes that UUID and adds it to the selected collection. In
other words, one can copy/paste from one collection to another, but
copy/paste in the context of the same collection has no effect. If you
paste into a collection that already has an item with that UUID, you get
a similar non-effect.
- "Paste" will be enabled if the clipboard has a format that is
appropriate for that view -- it currently doesn't take other context
into account (like whether or not the given uuid already lives in the
collection).
- "Duplicate" has no implementation for items currently -- we have a
context menu item (no top level menu item for item duplicate) and it is
always greyed out.
- "Cut" rarely works, in particular because you can't cut from
collections that are rolled up in the dashboard -- "mine" collections.
(What's up with that? You can delete and you can remove, but you can't
cut? Bryan added a workaround so that you get a dialog instead of just
failing.)
Here is what we *wanted* to happen (but punted for Preview):
- Copy/paste from one collection to another -- this *does work*, adding
the same item to the new collection was what we wanted.
- Copy/paste within the same collection, in calendar, was supposed to
create a custom recurrence rule. This got punted out of Preview, Bug 5461.
- Copy/paste within the same collection, in dashboard/table, was
supposed to do nothing, pending user feedback that some other behavior
was warrented. Presumably "Paste" should not be enabled in this case.
The "do nothing" part works brilliantly, the "don't enable paste in this
situation" requires a small bit of work.
- Duplicate was supposed to create an item with a new UUID -- "otherwise
identical in every way". Also punted, as part of Bug 5461.
- Two bugs related to disabling cut/paste for "read only" and other
"special" collections: Bug 8019 and Bug 8706. These had been punted from
Preview.
I think Andre's proposal is to disable cut/copy/paste (for items) at all
times. Are we sure that's what we want? We do lose the ability to use
copy/paste from one collection to another.
Perhaps it wouldn't be so hard to disable paste:
- for read-only
- for OOTB (Dashboard/Trash/In/Out)
- for collections that already have the item (slow?)
And then don't disable copy?
And completely disable cut? (Or somehow fix it up to use same code path
as delete/remove? Is there something I'm missing that makes this
unworkable?)
I currently have the bug: Bug 8706
https://bugzilla.osafoundation.org/show_bug.cgi?id=8706
Spec:
http://chandlerproject.org/Journal/DotSevenKeyboardShortcuts#DuplicatecutcopyPaste
Cheers,
Katie
Andre Mueninghoff wrote:
Hi, I would like to suggest for Preview that the menu option Edit-Copy
for items (also right-click an item in a table and select Copy) be
grayed out to indicate its unavailability, since it does not work
currently as recorded previously in [bug 8706]. Given the inherent
learning curve around what is the Dashboard, what are Collections, what
are items, what is stamping, etc., to have a relatively well understood
option seemingly available but not working, I think, is confusing to the
user. For example, my first thought was that, oh, this must have been
disabled in the Dashboard for some reason, only then to find that it
didn't work in a personal collection either. Additionally misleading is
that after one selects Edit-Copy for an item, the Paste menu item
changes from unavailable to available, rather convincingly suggesting to
the user that the operation is going to complete successfully.
Enjoy, Andre
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
