🚀 go-pugleaf

In article <463@psu-cs.UUCP> smethers@psu-cs.UUCP (Paul Smethers) writes:
>Secondly, you have my vote for as many key commands as possible.  Please
>never "replace" mouse commands for key commands, but have as many key command
>substitutes as possible.  

This does not work in instances where the purpose of the program is
to give the user access to data which is best 'viewed' rather than
concepualized.  For instance, when editing digitized sound, the
user interface design should visually provide the user with all the
information needed about the sound.  Instantaneous volume and sample
values are just two of the parameters that are best viewed graphically.
If a program was designed to give some mythical power user some features,
how could you hide those features in keyboard commands, when their
purpose is entirely graphical?


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Michael S. Czeiszperger     | "HELP!  I'm stuck in 3B HELL !!!"
Contracted to AT&T          | Phone: (614) 860-4952  (formerly with Ohio
Unix Systems Administration | UUCP: cbosgd!dkc1!czei  State University)
6200 E. Broad Street        | Disclaimer: "The above opinions are those of
Columbus, OH   RM 1L334     |              a large rodent with sharp teeth"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~