RE: standard key mappings

> Although I see your point, I must say that in this context I can't really
> see the problem with some degree of unification or how that would conflict
> with your 'pluggable' approach.

That is different to what was suggested though.

If I could code something to react to MAPPING_STANDARD_COPY and then let
another layer handle the binding between that and Ctrl+C or Ctrl+Ins, or
both (both together being the convention on Windows) or something else then
that would be a sensible coding standard that wouldn't impose itself on
users, but rather assist them.

There are still some problems though. Consider a mapping for "follow this
link in a new window". That mapping couldn't have existed before the release
of NN2, but is common enough now in browsers and other HTML-based
applications that it would be worth having a standard mapping for. Other
fields within computing would have similar needs arising at a rapid speed.

There can also be confusion as to how similar two concepts have to be before
they should use the same binding. The program I spend most of my time
working on has a text-editor with semantic mark-up. Should I use "b" (bold)
or "i" (italic) for as a shortcut for emphasise? (In the end I decided to
use "m" to deliberately avoid any link between emphasis and presentational
features).

Received on Monday, 29 July 2002 11:53:29 UTC