Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!netcom!chastain From: chastain@netcom.UUCP (Michael Chastain) Newsgroups: comp.society.futures Subject: Re: Looking Backwards Message-ID: <5469@netcom.UUCP> Date: 8 Jan 90 11:25:13 GMT References: <9001010220.AA17906@world.std.com> <752@arc.UUCP> Organization: NetCom- The Bay Area's Public Access Unix System {408 249-0290 guest} Lines: 32 [I apologize in advance if I've messed up posting to a moderate group. If I made a mistake, tell me how to do it RIGHT, ok?] In article josh@klaatu.rutgers.edu (J Storrs Hall) writes: >A better model is looking over the shoulder of a hotshot editor >wizard, pointing at the screen occasionally, and telling him what to >do. Over the phone, you can't see the screen, and you can't point. >Also realize that there will be a whole new generation of verbally- >oriented command languages, with idiomatic (and idiosyncratic) >contractions for commonly used operations. Here's what happens when I look over someone's shoulder now: "That assignment is wrong." "No -- THAT one." "You shouldn't be accessing that data structure." "That won't work, either." "Can I type? Move over." I can type vi commands faster than I can tell people what to do to text. What I would like is: two keyboards connected to the same workstation. The other person and I work out who is currently "active" by ordinary human body language / verbal communication. I.e., when I take my hands off my keyboard, it's his turn to type. No mechanism for indicating to the computer which keyboard is active. Such a mechanism would actually slow down my buddy and me. Michael Chastain "He who dies with the most FRIENDS wins."