From: Brantley Coile <brantley@coraid.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: First attempts
Date: Wed, 23 Aug 2006 23:05:03 -0400 [thread overview]
Message-ID: <44ED175F.1060905@coraid.com> (raw)
In-Reply-To: <7d3530220608231719p51206acxdf7c8004919b23e4@mail.gmail.com>
http://www.bitsavers.org/pdf/xerox/alto/AltoSchems/
John Floren wrote:
> On 8/23/06, David Leimbach <leimy2k@gmail.com> wrote:
>
>> On 8/23/06, John Floren <slawmaster@gmail.com> wrote:
>> > On 8/23/06, John Floren <slawmaster@gmail.com> wrote:
>> > > On 8/22/06, Dave Eckhardt <davide+p9@cs.cmu.edu> wrote:
>> > > > Personally I'd like to see a "Maze War" clone (that was perhaps
>> > > > the original first-person-shooter game). I bet there's code
>> > > > kicking around you could start from. You could do an IP version,
>> > > > or maybe use a set of named pipes on a handy Plan 9 file server
>> > > > to do your networking instead.
>> > > >
>> > > > Dave Eckhardt
>> > > >
>> > >
>> > > I saw something a few months ago about Maze War; it was perfect with
>> > > the mouse and chording keyboard thing.
>> > >
>> > That's what I get for not paying attention. I meant to add that this
>> > was Maze War on the Alto, which of course was the machine that *had*
>> > the chording keyboard.
>> >
>> > John
>>
>> I think I want a chording keyboard too... I wonder who could be
>> convinced to make one since my EE-fu is possibly the worst ever.
>>
>
> Well, first ask Xerox for the schematics and specs on theirs... I
> wonder if they would give them to you, since they no longer produce
> it. Perhaps if you assured them you only want to make one unit for
> yourself, they would. Of course, then you have to convert from
> whatever their unit outputs to PS/2, but it would be a nice thing to
> have.
>
> If you get anywhere, find any schematics, etc., post them here or send
> them to me. My EE-fu might be sufficient.
>
> (New subject) Weren't the chording keyboard and the mouse designed to
> go together? If I could type with one hand while having the other on
> the mouse, I could see how Plan 9 would be *perfect*. As it is, I
> still get annoyed when I have to take my hands from the keyboard (yes,
> I've read all the stuff about how it isn't /really/ faster, but I
> can't really believe that it's faster to grab the mouse and click than
> it is to alt-tab--at least in some cases).
>
>
> John
next prev parent reply other threads:[~2006-08-24 3:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 16:26 [9fans] " Jared Norman
2006-08-22 16:33 ` erik quanstrom
2006-08-22 16:37 ` andrey mirtchovski
2006-08-22 16:54 ` John Floren
2006-08-22 16:57 ` andrey mirtchovski
2006-08-22 16:59 ` jmk
2006-08-22 17:03 ` John Floren
2006-08-22 17:07 ` jmk
2006-08-22 17:09 ` John Floren
2006-08-22 17:16 ` erik quanstrom
2006-08-22 17:22 ` jmk
2006-08-22 17:32 ` elbing
2006-08-22 17:36 ` John Floren
2006-08-22 17:42 ` erik quanstrom
2006-08-22 17:11 ` Sape Mullender
2006-08-22 17:13 ` Lyndon Nerenberg
2006-08-22 17:11 ` andrey mirtchovski
2006-08-23 3:05 ` [9fans] " Dave Eckhardt
2006-08-23 20:44 ` John Floren
2006-08-23 21:12 ` John Floren
2006-08-23 22:22 ` David Leimbach
2006-08-24 0:19 ` John Floren
2006-08-24 3:05 ` Brantley Coile [this message]
2006-08-24 14:34 ` John Floren
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=44ED175F.1060905@coraid.com \
--to=brantley@coraid.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).