9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Lukes davel@morgan.com
Subject: keyboard accelerators
Date: Mon, 24 Apr 1995 16:24:47 -0400	[thread overview]
Message-ID: <19950424202447.LUqDXQ4vhLK0N-8geXIZsHwCYLbJ3j5Ntt2zCZe2Z84@z> (raw)

> >keyboard accelerators are indicative of a broken user interface.

Boyd is, as usual, right.

> Not everybody is coordinated enough to use a mouse efficiently.

Ditto keyboards.

Let's not be restrictive:
many of the people here use trackballs instead of mice,
because they don't have the desk space to conveniently move a mouse around.

The input *device* isn't under discussion here:
it's what you expect it to do with it:
either to indicate geometric information,
or to input things which are commonly interpreted as characters,
but might be used for other event-like stuff.

> My mother has difficulty, for example.  Even worse, some people
> have genuine physical handicaps who *cannot* use a mouse, but who
> can use some form of keyboard.  Or vice versa, for that matter.

This says more about the inadequacy of input devices than about input
paradigms.

Even though I'm, fairly able bodied,
I've wanted one of those neat eye movement things,
so I can just look where I want to,
instead of having to move the mose/spin the ball/waggle the joystick/whatever.

> Recently my mouse broke.  It was a weekend.  Under X, I was completely
> paralyzed.  I rebooted my PC to Windows (blech!) and was able to get
> some useful work done in a multi-window environment.  It was painful,
> but better than the complete paralysis under X.

So you window manager sucks:
what has that got to do with the price of mice?

To be fair to X (not that it deserves it),
there's nothing that I am aware of that forces you to use a mouse:
some window managers (olvwm, for one),
can (theoretically) have a mouseless interface,
parts of which I occasionally use (when I'm forced to use a trackball).

> (Argh, mice are expensive.)

(And they nearly all suck!)

> Supporting multiple styles of input strikes me as generally useful.

Well I'm afraid I disagree:
supporting multiple input *devices* may be useful.
but if you have a good input style, why clutter things with an inferior one?

> I don't think it necessarily implies software bloat.

(All together now children):
 OH YES IT DOES!!!!

	Dave.






             reply	other threads:[~1995-04-24 20:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-04-24 20:24 David [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-04-27  0:00 Castor
1995-04-26 22:52 Felix
1995-04-26 20:07 serge
1995-04-26 12:23 rob
1995-04-26  7:19 Heiko
1995-04-26  1:05 Scott
1995-04-26  0:16 serge
1995-04-24  8:22 Nigel
1995-04-24  5:15 Felix
1995-04-24  4:22 Mike
1995-04-24  3:13 ozan
1995-04-23 23:30 Boyd
1995-04-21 22:20 forsyth
1995-04-21 16:45 Don
1995-04-11  9:54 Nigel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19950424202447.LUqDXQ4vhLK0N-8geXIZsHwCYLbJ3j5Ntt2zCZe2Z84@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).