Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!uwvax!astroatc!nicmad!madnix!zaphod
From: zaphod@madnix.UUCP (Ron Bean)
Newsgroups: comp.misc
Subject: Re: Optimal keyboards
Summary: Chord keyboards aren't supposed to be fast...
Message-ID: <1523@madnix.UUCP>
Date: 2 Sep 90 14:54:17 GMT
References: <24190@uflorida.cis.ufl.EDU> <1990Aug25.015334.16702@nmt.edu> <1990Aug30.005509.2877@athena.mit.edu>
Organization: MADNIX, operated by: ARP Software  Madison WI
Lines: 23


   It doesn't matter how slow a chord keyboard is, because it's not
supposed to _replace_ the full keyboard; it's supposed to _supplement_ the
mouse. You still enter text the usual way; you use the chord-keyboard
(which its inventors at SRI called a "keyset") to make corrections and give
commands while your other hand is "mousing around" (or otherwise occupied).
 
   It's interesting to see how often this request pops up these days; it's
about time something appeared on the market. The people at SRI reported
that it only takes about a week to become proficient (the microwriter
people claim 15 hours), and I've heard that IBM has studied the idea as
well.
 
   Actually, it could be done entirely in software-- with your right hand
on the mouse, lay your left hand on the 'home row' (ASDF), with your thumb
on the spacebar. That's not too bad a position for typing "chords"; you
just need a device driver to decode it properly (I'm assuming your keyboard
sends separate make/break signals). Maybe someone like Northgate could
build it into their keyboards.
 
==================
zaphod@madnix.UUCP (Ron Bean)
{harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!zaphod