From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] The utility of a chording pad
Date: Tue, 6 Nov 2007 15:49:56 -0600 [thread overview]
Message-ID: <a4e6962a0711061349k711d2eb6s4cc320814a29d42d@mail.gmail.com> (raw)
In-Reply-To: <7204efbdee8bf0cec2284a4f8ed64276@csplan9.rit.edu>
On 8/4/07, john@csplan9.rit.edu <john@csplan9.rit.edu> wrote:
> So I've spent a lot of time today watching recordings of Engelbart's
> 1968 demonstration (http://sloan.stanford.edu/mousesite/1968Demo.html),
> and I really like the chording pad he has over on the left of his keyboard.
> It's the same type of thing that shows up again in the Xerox Alto.
> I'm just wondering, as Plan 9 users and developers, what would you do
> with such a thing in the environment? Engelbart's device apparently
> let you input 31 different chords, which I'd say isn't sufficient to replace
> a keyboard but is still pretty impressive; with such a thing, would you perhaps
> bind the chords to perform acme commands, for instance? We've already
> got mouse chording, and it's pretty slick; add some more chording in,
> say hit the first two keys in order to delete the current frame in acme.
> Of course, if we were to get a chord pad that could produce enough
> combinations for all alphanumeric characters, it could be used to replace
> the keyboard.
>
> I'd just like to get some opinions, see what you think of chording devices
> and what potential utility they could have in Plan 9.
>
I always thought it'd be cool to hack up something for
http://catalog.belkin.com/IWCatProductPage.process?Product_Id=157024
to do left handed chording and keep the right hand on the mouse.
I bought one and played around a bit, but was unsatisfied with my
ability to actually detect chords without writing a proper driver
IIRC.
I experimented a bunch with different chording setups a decade ago and
found most unsatisfactory, but half-keyboard chordic setups seem to be
quite easy to pick up - the problem with the Nostromo was that it was
like 2 keys short of being a proper half keyboard so you needed more
than one meta-key ... which was offputting. Plus no numbers made it
kinda hard to code with.
-eric
next prev parent reply other threads:[~2007-11-06 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 3:50 john
2007-08-05 10:03 ` Lucio De Re
2007-08-05 15:53 ` Jack Johnson
2007-08-05 10:05 ` Gabriel Diaz
2007-11-06 21:49 ` Eric Van Hensbergen [this message]
2007-08-05 11:35 erik quanstrom
2007-08-05 11:49 ` Lucio De Re
2007-08-05 11:59 ` Lucio De Re
2007-08-05 14:19 ` Steve Simon
2007-08-05 15:33 ` Lucio De Re
2007-08-05 15:33 ` Skip Tavakkolian
2007-11-06 21:26 ` maht-9fans
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=a4e6962a0711061349k711d2eb6s4cc320814a29d42d@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
/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).