Roadmap

This is very incomplete at current but should give you a sense of ongoing work

We are working to get a compiled version of Sirikata made available for 7/22/09

Sirikata content tools

• version 0.01
• Anticipated release date: 7/22/09

Objects:

• import
• drag/drop on Windows
• key/text input on other platforms
• local upload or upload to CDN? (if just local, how do we get this data into the CDN?)
• placement
• mouse, text tweaking (scene.txt?)
• orientation (Chris claims just text, but -- Euler values? (rotations are hard to describe in text -- can't use Quaternions!) (we cannot use existing UI sliders to rotate 360 per direction? -J)

I think a simple pitch/roll/yaw interface will be not hard to code & very useful -- 'P', 'R', 'Y' (this isn't intuitive to most people, but that can be fixed in future with a gizmo that shows the direction, -J)

• Pitch - mouse Y rotates object around X axis (left of screen to right, through object))
• Yaw -- mouse X rotates object around Y axis (Y = vertical, from ground to sky through object)
• Roll -- mouse X rotates object around Z axis (from camera through object)
• scaling
• mouse & text tweak
• delete
• object properties (for now, physics properties: collision, dynamics, hull type)

MiTo Specific Object requests:

• Looped animation of translation
• rotating infinitely in a single direction
• rotate 1 direction then return to origin loop repetition infinitely (like a hammer swing)
• Scatter
• select a series of objects and have them scatter from a central axis/point (explode effect)
• Cell or Bounding Box of a mesh coordinates and player coordinates sent out to OSC

Lights:

• placement
• direction (kind of like rotation, but it would be much more intuitive to have them 'point' at a 3D location, perhaps using a selected object?
• attributes (directional, specular, ambient?? whatever)
• Light trigger (off/on)

General:

• save scene
• short-term, I assume this is still a text file. I would like to change the format to something reasonably editable, like .csv (can open in ooffice and edit by row/column)
• I think import from meru should be differentiated from scene save/load, they have somewhat different requirements
• there may need to be a specific feature to upload the scene, ie make sure all newly imported content is on the CDN