On Jan 12, 2014, at 5:53 PM, Igor Stasenko <[email protected]> wrote:
> And modal popups is clearly against this principle. > Because they > a) make you think > b) draw your energy from what you really should be thinking on.. > > so please explain, how adding yes/no popup to cmd-L command handling helps > maintaining this principle better. Some designers think that dialogs (stateful interfaces) are the enemy of usability, and I'm in favor of using them as last resort. Also because users in general, not only programmers, have hard feelings about dialogs What I wasn't checking (lack of usability tests I'm watching you... yet.. again...) was which workflow exactly were you talking about. The cmd-L contains explicit information about discarding changes so asking confirmation is unnecessary. (I thought you were talking about changing focus or the selected method on a browser and discarding changes without asking, sorry if I confused you). Usability tests solves all this and a lot more in half a second. Ok, I'm experimenting a little here and A) Cmd-L is something hidden enough to not be seen by newcomers and B) I get that you can produce an interesting workflow if you are used to do something and use cmd-L as a fast way to undo changes I wasn't even knowing about cmd-L existence, how anybody knows about it? If you ask me what I do for the same case, I'm used to go to method versions and revert to the desired one
