- the navigation window. a visual, abstract representation of oudeis, which
will be used to 'navigate' the performance (tim=F3n / rudder / Steuerruder).
with Aaron we were thinking about this as some kind of 3D image in which
you can move around a central object and 'get into it' from different
sides. if we do the 'oudeis ship' application i would put this on a window
by its own.
- the main stage window. in it you should be able to see the performance as
if you were in any of the real stages or as a purely virtual thing or
(wonders of technology) as a purely real thing. the problem here is the
visualization of the actors. i guess we can put some kind of picture for
the real ones and a lightcone graphic for the virtuals, but i fear this
will look like a puppet theatre!
- the MOO window. the program should connect you to the MOO as soon as you
open the window and transport you to a theatre seat. you can speak into the
MOO, probably like on a simple MOO client, by having a separate pane for it.
- the choros window. in it you should have two parts: control and feedback.
control is where you click to send a choros-event instruction, feedback is
where you receive a graphic showing you the status quo of the next stasima,
and where is your song going to be. this feedback window would animate
during the stasima, so everybody can understand how the song thing works.
- the net feedback window. a small one, showing some net numbers or graphs.
- the 'translation' window, which should show the text in english or in the
language of your choice.
- a 'control panel' window. where you can control the volume of the sound,
and probably some other things.
note: you should be able to close any of this windows, to move them on your
screen, etc.
additions?
best,
santiago
music is dressed silence
mailto:jaco@overnet.com.ar
http://www.geocities.com/~yaco