Xref: utzoo comp.windows.misc:879 comp.sys.next:1086 comp.sys.mac:24537 comp.cog-eng:777 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!encore!gloom!cory From: cory@gloom.UUCP (Cory Kempf) Newsgroups: comp.windows.misc,comp.sys.next,comp.sys.mac,comp.cog-eng Subject: Re: One Step... (part 2) Message-ID: <283@gloom.UUCP> Date: 30 Dec 88 15:53:23 GMT References: <264@gloom.uucp> Reply-To: cory@gloom.UUCP (Cory Kempf) Organization: Alloy Computer Products, Framingham Mass. Lines: 30 In article eric@snark.UUCP (Eric S. Raymond) writes: >In article <264@gloom.uucp>, cory@gloom.UUCP (Cory Kempf) writes: >> The other article that I wrote gave a nice discription of how I >> envision the next generation of userinterfaces to work. > >Neat description, but I spot a major problem. With no tactile feedback on >the phantom keyboards, how are ya gonna type? Are you assuming something >like a dataglove that can generate pressure on the hand to simulate touch of >the virtual objects? If so, realize that that is a *very* hard problem just >from the mechanical-effector point of view. uh, just what made you think that I was not planning on generating feedback? Whan I was in college, I started designing a project for an electronics class that did just that... motion detection AND feedback. The method that I came up with was (necessarily) a low budget approach, but the prof seemed to think that it was possible to develop. The version that I designed was a mitten approach for simplicity, and didn't use stepper motors in order to cut costs. One of these days, (when I get rich) I would like a chance to build the system the way it should be done... (I think one of the reasons that I was able to design the system was that nobody thought to tell me that it couldn't be done :-) ) +C -- Cory ( "...Love is like Oxygen..." ) Kempf UUCP: encore.com!gloom!cory "...it's a mistake in the making." -KT