Eugene, (01)
Thanks for posting this. This matches the information at
http://www.bootstrap.org/augdocs/augment-14851.html#2C3, except that
this page seems to document the left-most two buttons being used at
once, while Jeff recalls that all three buttons were used. That would
be an issue on the normal two-button mouse, which uses both buttons
down to simulate the third button. On some mice with scrolling
wheels, the wheel is also a button that acts as the middle
button. I'm really stumped about we'd do on a Mac, which has a
single button mouse that relies on keyboard modifiers to simulate the
other buttons. (02)
I'm starting to accumulate information on commercially available
chordic keyboards, past and present. For one, it might allow us to
use a commercially available one rather than having to build one if
John's company isn't able to do this for budget or scheduling
reasons. For another, it will be useful to show the evolution of
these devices starting with the original keyset. There are a couple
of promising ones out there in production, including: (03)
http://www.bellaire.demon.co.uk/newcykey.htm
http://www.infogrip.com/product_view.asp?RecordNumber=12 (04)
Neither of these are exact matches for Doug's keyset, but either
could be easily learned by new users. We'd want to write new drivers
so that they behave like Doug's keyset. (05)
I have to run to a meeting, so I'll send you pointers to the sites
later today or this evening. (06)
Would Jeff like to be on the nls-technical list to track what's going
on with the nls-restore project? Would you be interested in setting
up cross-posting between nls-technical and bootstrap-nfs? (07)
At 09:39 AM 2/13/2006, Eugene Eric Kim wrote:
>I'm forwarding a message that Jeff Rulifson sent to our internal
>project mailing list so that the rest of you can read it.
>
>We're starting to suffer from silo clash with these cross posts to
>various closed mailing lists. I'd like to propose that we move this
>discussion to hyperscope-dev@blueoxen.net, as this discussion is
>relevant to all of us and I'd like it to be publically archived.
>Instructions for subscribing are at:
>
>http://blueoxen.net/c/hyperscope/wiki.pl?MailingLists#nid7
>
>On a related note, is there a public site for the Augment NLS
>Restoration Project? We're going to be scavenging / creating a lot of
>technical notes on Augment, and I'd also like those to be publically
>available as well.
>
>-Eugene
>
>----- Forwarded message from Jeff Rulifson <jeff@rulifson.name> -----
>
>Date: Sun, 12 Feb 2006 20:58:22 -0800 (PST)
>From: "Jeff Rulifson" <jeff@rulifson.name>
>To: <bootstrap-nsf@ws.blueoxen.net>
>Subject: [bootstrap-nsf] Re: chord keyset
>Reply-To: bootstrap-nsf@ws.blueoxen.net
>
>Everyone: Some history -- As I remember the SDS940 implementation, the OS
>concatenated the three mouse bits with the 5 chord keyset bits to make an 8
>bit character. The keyset was the low order 5 bits and the mouse was the top
>3 bits. This produced 255 characters.
>
>These characters were remapped to match the octal ASCII characters from the
>keyboard. I.e., when used with the left hand a single stroke with the left
>thumb produced a 001 which was remapped into a 061 to match the "a" from the
>keyboard. I remember this because, when reading a core dump, we could all
>decode octal strings by putting down our left fingers and feeling the
>character. 123? Hmmm, left ring finger, index finger, and thumb. That's an
>"s". Given that one understood how upper and lower case were mapped.
>
>The mouse buttons could be used 1, 2, or even 3 at a time to produce the top
>3 bits and give the full 255 character ASCII character set.
>
>The character stream from the mouse/keyset was merged with the character
>stream from the keyboard. The high level user interface code did not
>distinguish between keyboard input and mouse/keyset input.
>
>I'm reporting this because I began to wonder how mice work today. Can they
>report simultaneous clicks? To get the same effect as the 940, will the
>mouse driver also need to be redone? Will that even help? Are they hardware
>limited and can only report one button at a time?
>
>Maybe there is a better way that will fit with available equipment?
>
>Jeff
>
>--
>======================================================================
>Eugene Eric Kim ......................... http://public.xdi.org/=eekim
>Blue Oxen Associates ........................ http://www.blueoxen.com/
>======================================================================
>
>_________________________________________________________________
>Message Archives: http://chm.cim3.net/forum/nls-technical/
>Shared Files: http://chm.cim3.net/file/work/project/nls-restore/
>Community Portal: http://www.computerhistory.org/
>To Post: mailto:nls-technical@chm.cim3.net
>Community Wiki: http://chm.cim3.net/cgi-bin/wiki.pl?NLS_Restoration (08)
Philip Gust
Nouveau Systems, Inc. (09)
phone: +1 650 961-7992
fax: +1 520 843-7217 (010)
mailto: gust@NouveauSystems.com (011)
_________________________________________________________________
Message Archives: http://chm.cim3.net/forum/nls-technical/
Shared Files: http://chm.cim3.net/file/work/project/nls-restore/
Community Portal: http://www.computerhistory.org/
To Post: mailto:nls-technical@chm.cim3.net
Community Wiki: http://chm.cim3.net/cgi-bin/wiki.pl?NLS_Restoration (012)
|