On Mon, 13 Aug 2001, Paul Rohr wrote: > > If you want to optimize the UI for ultra-rapid access to very commonly-used > operations (such as line and page breaks), that's a logical place for > keybindings. That's why most of those had already been committed by October > 1998 (rev 1.3), with simple section breaks getting added as "late" as > February 1999 (rev. 1.20): > > > http://www.abisource.com/bonsai/cvslog.cgi?file=/abi/src/wp/ap/xp/ap_LB_Defa > ult.cpp > > Note that only the more complicated variants of section breaks don't have > keybindings already -- but that makes sense for two reasons: > > 1. Unless you're developing or testing the feature, those variants are > *very* rarely used. > > 2. The differences between them are subtle enough that they *beg* to be > explained, and a dialog is a much easier place to get help in a UI than some > pull-right menu. > > In short, all we need to do here is follow standard GUI design practices: > > - use the keyboard for quick access to high-frequency tasks > - use dialogs for easy discovery & explanation of the same functionality > > Does that make sense? > Sure. However we need to make sure the kyebindings are visible to the user. I guess they should be displayed in the break dialog somehow so users can discover them as they use the program. Training by using :-) Cheers Martin
