Xref: utzoo comp.std.misc:155 comp.windows.misc:1157 comp.misc:6549 comp.periphs:1904
Path: utzoo!utgpu!watmath!att!bellcore!rutgers!iuvax!cica!ctrsol!uakari!ark1!dsill
From: dsill@ark1.nswc.navy.mil (Dave Sill)
Newsgroups: comp.std.misc,comp.windows.misc,comp.misc,comp.periphs
Subject: Re: User Interface Standards -- *Keyboards!*
Keywords: keyboards,standardize,plug-n-play,freedom,ADB
Message-ID: <13@ark1.nswc.navy.mil>
Date: 14 Jul 89 13:47:40 GMT
References: <115518@sun.Eng.Sun.COM>
Reply-To: dsill@relay.nswc.navy.mil (David Sill)
Organization: Naval Surface Warfare Center, Dahlgren, VA
Lines: 24

The best keyboard proposal I've heard consists of defining a standard
hardware/software interface between the terminal or computer and the
"keyboard".  Of course, there'd have to be codes for all the printable
characters, control characters, meta-characters, cursor movement,
function keys, etc.  It should also include provisions for
non-character-based input, i.e., graphic pointer movement
(mouse/trackball/joystick), and button clicks.

Most equipment would come with a "standard" qwerty keyboard, but third
party vendors would supply various alternatives including smart
keyboards, keyboards with built-in trackballs, digitizing tablets,
voice recognition boxes, handicap input devices (like the one Stephen
Hawking uses), etc.

Serious hacks would carry their keyboards around with them from
machine to machine replacing whatever keyboard was provided.  They'd
never have to worry about adjusting to a different keyboard.

I don't know much about Apple's Desktop Bus, but it may be something
like what I'm talking about.  If so, it sure seems like some third
party vendors are missing an opportunity.  Can anyone familiar with
ADB comment on this?
-- 
-Dave (dsill@relay.nswc.navy.mil)