"Norton, Chris" wrote:
> 
>         KeyboardPolicy (this would be the "standard" Squeak keys)
>            Kb101KeyPolicy
>            KbMacintoshPolicy
>            KbWindows95Policy
>            KbCustomPolicy (you could re-map your own preferences here)

Just brainstorming here...

One thing I'd like to see in KeyboardPolicy: a mechanism that maps a
keyboard event into various editing/text cursor movement events. Events
borrowed from the Windoze world include:
  One character ahead/back
  Word ahead/back
  Paragraph ahead/back
  Page up/down
The above four (eight) ones with and without selecting the text being
jumped over. (In Windows, if you move the cursor and hold the Shift key
pressed, all text between the initial cursor position and the position
after cursor movement will be selected. This works regardless of whether
you move the cursor via keyboard or mouse. Very handy. I'm not sure how
to model this best; other platforms might have an entirely different
policy.)
  Cut
  Copy
  Paste
  Undo
Several keys should be able to map to the same action (Undo can be both
Ctrl-Z or Alt-Backspace under Windows); one of the combos would be the
"preferred" one.
It should be possible to ask an action which key is its preferred one.
This would be highly useful to decorate menu entries and action buttons
so that the user can see how he can navigate the program via keyboard.
This makes for *very* fast learning; those combos that you need often
are automatically looked up for you, and you use them once you decide
that you want to be faster; if you forgot a key, no problem: just use
the mouse, and you'll immediately see what you forgot (and remember
better next time if you really care about that keyboard command).

Some more general commands:
  Help
  next/previous Window
  Menu bar (F10 in Windows; you can navigate the menu bar with cursor
keys afterwards, and either abort by pressing Esc or confirm by pressing
Return)
  Abort (commonly bound to Esc)
  Confirm (commonly bound to Return)

It would be highly desirable to allow windows to define their own
keyboard command schemes. This way, people could experiment and define
bindings as they see fit (and the framework would be able to decorate
menu entries automagically).

Regards,
Joachim
-- 
Please don't send unsolicited ads.