See Sparrow Page of iSpaces Module 5, Post-Desktop Interfaces
"Can we speed up and simplify setting up experiments with different user interface hardware configurations in an augmented-reality environment such as the Stanford iRoom, by providing a toolkit of basic, generic physical input and output devices that are new in that they are completely mobile, untethered, and remotely accessible through the room software infrastructure (event heap), and that can therefore be combined on-the-fly to build or extend physical post-desktop user interfaces?"
This means that our "users" would in fact be primarily developers who wish to assemble post-desktop GUIs quickly using our toolbox, although more mature technologies could be turned into permanent, end-user interaction devices as well (like an iButton to get the iRoom into a certain state, etc.)
- Have the GroupStorm project run 2 experiments, one without and one with an "iLight" on their graphics tablets to provide user feedback about the state of the tablet. Interview the GroupStorm developers to find out whether the iLight made their task of administering these 2 experiments easier, compared to having to custom-build a feedback light to go onto the Wacom tablet.
A similar argument could be made for other devices. For example, an iButton could be added to the eBeam pen system that Andy Milne from CDR is using, to be able to compare it more easily with our Wacom solution for GroupStorm.
Make existing technology (iButtons) robust and document it
One-bit Ubiquitous Devices (Josh's old iButton project description - now with parts list)
Josh's new iButtons FAQ
iButton sender & receiver schematics and wiring diagrams (Josh, by Nov. 2)
Robust new receiver on printed circuit board (Josh, by Nov. 9)
New iButton in SMARTboard pen form factor, to test quality of documentation (Michael, by Nov. 9)
Research other existing projects in physical widgets:
-> Result: iStuff-related source list
Define salient scenarios of use for intended new devices
Define features and performance parameters for new devices
Build series of physical/electrical prototypes (from foamcores to final devices) to find best form factors
Extend existing programming support and user interfaces to integrate devices into the iRoom infrastructure
Prove that devices make it easier to design interfaces for ubiquitous computing, using iRoom UI developers as subjects to begin with.
Document technical construction, software APIs, design process, and evaluation process and results
Voice control: control iRoom elements with voice commands.
Jan Borchers <firstname.lastname@example.org> • Last modified Feb. 24, 2002 9:30 pm