Sean, kilon,
in fact Pharo has some of that, through RB and it's ability to undo / redo code
change actions and combine them. I did for AltBrowser move to RB actions
instead of the usual ones for some code related commands (class remove, class
rename) and added a generic "undo" command with the RB related one, but I
stopped halfway through it with totally unfriendly names for the undo commands
(not fun to have a 100 characters + description of the undo in a menu item !)
and lazyness in reworking some operations (method change) so as to integrate
them as a RB operation transparently. My knowledge of the RB commands isn't
good enough also to understand all the possibilities if we have a GUI
associated.
At least I do have a class remove without a confirmation dialog ;) and a
possible undo.
Once we'll have something like EPICEA integrated, I guess we will be able to do
that in most cases for code related actions as well.
Sean, I like what you described with Growl. This could prove very nice and
sleek to have.
Thierry
________________________________________
De : Pharo-dev [pharo-dev-boun...@lists.pharo.org] de la part de Sean P.
DeNigris [s...@clipperadams.com]
Date d'envoi : mercredi 8 janvier 2014 22:22
À : pharo-dev@lists.pharo.org
Objet : Re: [Pharo-dev] Do you want to accept???????? Discard???????
kilon wrote
> The only thing that would make sense for removing confirmation dialogs is
> editable action history. Take a look at Photoshop. Some 3d apps also have
> something similar. Every action is recorded at a history ( a list) and
> there is a gui that allow you to remove individual actions without
> deleting or affecting other actions. Very cool stuff.
Yes! That would be a dream. I was thinking last night that undo could be a
tree from high level concepts down to individual actions. Something like:
- edit #aMethod
- paste
- delete
- backspace
- backspace
- edit #anotherMethod
- …
kilon wrote
> Undo also wont do, because I dont always realise my mistakes until much
> later on. And having to undo all my work to fix a stupid mistake is a
> nightmare.
Certainly it seems too harsh to throw away without any notification. For
now, I think the sweet spot for most people would be undo + non-instrusive
notification. Maybe an undo list like "Workspace previous contents" and a
Growl notification. If someone reaaaally needs the confirmation, we could
have a setting, but we're talking about a single method pane's edits -
overkill IMHO...
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Do-you-want-to-accept-Discard-tp4735220p4735268.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
