VRG3D Requirements: Difference between revisions

Revision as of 16:31, 15 December 2009

Let new users get started in a few minutes through online documentation
Create rich immersive virtual worlds with high update rates and low-latency
Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.
Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)
Interoperate (to some degree) with geometry and color calibration system
[MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos”

documentation
- "make doc" makes doxygen style documentation
- it's possible to make introduction page...
examples
- lowest-level events
have short-term milestones & then get guinea pigs to test it (is it actually easy to use?)
synching
interaction
3D graphics
multiple displays
multiple OS's
testability
"easy-of-use"
code repository & code access

@@ Line 1: / Line 1: @@
+== High-level goals ==
+# Let new users get started in a few minutes  through online documentation
+# Create rich immersive virtual worlds with high update rates and low-latency
+# Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.
+# Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)
+# Interoperate (to some degree) with geometry and color calibration system
+# [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos”
 == VRG3D Requirements ==