the oudeis ship would _be_ the webstage. in fact a different webstage for
each spectator, since they will change the way it looks (i.e. opening some
of the windows and not others, participating in the MOO, clicking on the
choros, etc.)
>but as you wrote it down, it is mainly a bunch of windows they can
>choose?
>wouldn't an additional applet slow it down even more?
the idea would be to use the application _instead_ of using a browser.
audience should download this thing before the performance.
this would in fact make the whole thing a lot (a lot lot) faster, for two
reasons:
- a browser takes care of lots of things, has lots of capabilities, and
thus is not the best at anything (there's a saying here, something like 'he
knows a bit about everything but nothing about anything')
- most of the images can be within the program, so there's no need to
download any graphic files during the performance but the ones generated in
real-time. (i.e. every time i connect to oudeis' website i have to download
the big logo. if i had the logo on my computer, i wouldn't have to download
it. by using the program --the ship-- i wouldn't even have to wait for the
image to appear.)
>should we give our audience the impression to enter a ship? to "go on a
>trip" with us, exploring oudeis??
i think this is a good one. maybe this can be done for the we audience
during the parodos or when they open the program (like those windows that
appear when you open programs like netscape of office programs, but with an
animation).
best,
santiago
music is dressed silence
mailto:jaco@overnet.com.ar
http://www.geocities.com/~yaco