PiRSquared17 / specto

Automatically exported from code.google.com/p/specto
0 stars 0 forks source link

undo instead of deletion confirmation #139

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
I will admit here that the confirmation dialog that appears when deleting a
watch was there because I lacked (or so, back then at least) the competence
to implement an undo/redo system.

So yeah, we need undo.

One way to do it that comes up in my mind is to just store deleted watches
into a list variable (with all of their information), clear the cache, and
then remove the watch. If the user wants to undo, we just need to fetch the
latest item in the deleted watch list variable.

Of course this python list would be automatically lost on restart.

Original issue reported on code.google.com by nekoh...@gmail.com on 21 Apr 2008 at 10:41

GoogleCodeExporter commented 9 years ago
Please note that in current version (0.2.2), the "deleting watch" function is 
not
directly accessible and doesn't have confirmation dialog
I guess you're talking about development branch

Original comment by thibaut....@gmail.com on 21 Apr 2008 at 10:55

GoogleCodeExporter commented 9 years ago
So if i understand correctly,  you want to remove the confirmation and instead
implement undo/redo?
Why this would be better than the confirmation? I dont really see the use if we 
have
a confirmation because i think the user is sure to remove it if i answers to 
remove
the watch in the confirmation

Original comment by woutclym...@gmail.com on 22 Apr 2008 at 5:42

GoogleCodeExporter commented 9 years ago
Never Use a Warning When you Mean Undo (Aza Raskin)
http://www.alistapart.com/articles/neveruseawarning

Original comment by thibaut....@gmail.com on 22 Apr 2008 at 9:45

GoogleCodeExporter commented 9 years ago
from GNOME HIG :

If an action is very dangerous, and there is no way to undo the result, warn
the user and ask for confirmation. Only do this in extreme cases, though; if
frequently faced with such confirmation messages, users begin to ignore them,
making them worse than useless.

In all cases, the user's work is sacrosanct. Nothing your application does
should lose or destroy user's work without explicit user action.

http://developer.gnome.org/projects/gup/hig/2.0/principles-forgiveness.html

Original comment by thibaut....@gmail.com on 22 Apr 2008 at 9:50

GoogleCodeExporter commented 9 years ago
The problem is that, as I thought, implementing this is quite hard for the 
minimal
return-over-investment (after all, specto doesn't manipulate "complex 
documents", it
doesn't require multi-step operations, etc.)

http://dotsony.blogspot.com/2009/04/okay-take-deep-breath.html

Original comment by nekoh...@gmail.com on 25 Apr 2009 at 12:13

GoogleCodeExporter commented 9 years ago
so bad :-(

yesterday i was thinking again about that issue while deleting a watch
i would have liked not be disturbed by a popup window asking me if i'm sure 
while
trying to delete it whereas an undo menu entry would have avoid all these popup 
windows

Original comment by thibaut....@gmail.com on 25 Apr 2009 at 5:52