Hi Folks,

I've been working on various remove related bugs (6938, 6960, and 7599),
and I realized there's enough design ambiguity in all these that I ought
to be asking questions on the design list and spelling out the behavior
I'm going to change.

Currently, remove behavior approximates the behavior described in the
0.6 Remove and Delete spec,
http://svn.osafoundation.org/docs/trunk/docs/specs/rel0_6/RemovalAndDeletion-0.6.html
(look for the table that starts with the text "Deleting/Removing Items").

Since that spec was written, we've changed what the DEL key maps to.
Pressing DEL used to do a delete (move to the trash, don't show in any
other collections), now it does a remove (conceptually, take the item
out of the currently selected sidebar collection).

It would be nice to always let the DEL key do SOMETHING if it's pressed,
but right now remove is disabled in various instances.  To achieve this,
bug 6938 suggests that when remove is equivalent to delete, instead of
disabling remove, we should pop up a confirmation dialog.  I think
that's a fine idea.

There's some question about what should happen if the dashboard is
selected but the current item is only in the dashboard because it's in a
mine collection (bug 6960).  Currently we only allow delete from the
dashboard in this circumstance, not remove.  Excluding the item from the
dashboard but leaving it in it's source collection is one possibility,
but I think breaking the mine-implies-in-dashboard rule is liable to
confuse people.

Another option would be to pop up a dialog in this case, too, explaining
that removing from the Dashboard is equivalent to delete, giving the
option to cancel.  This seems like a good path to me.  We could even add
a "keep source collections out of dashboard" option, which I think might
be a pretty useful feature.

Finally, what should it mean to remove an item from other out-of-the-box
collections, like In and Out?

Sincerely,
Jeffrey
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design

Reply via email to