i'm downloading the thing so i can test it. for the java part, i'm studying
that a lot (one RL book and about 7 or 8 'digital' ones, downloaded the
soft for writing it, etc.) i know aaron & christian are working in a java
project also, and they can write java easily, so the team should be ready
for this. what we need to do (as i wrote before) is to decide what to put
on it.
about the applet vs. application thing: anyway the user will have to
download something. the problem is that if we do an application each user
will have to download the 'oudeis ship' _and_ the java Virtual Machine. if
we do an applet (or a group of them), the user will be able to use it from
the browser, but then we have the speed problem. my big doubt here is that
i'm starting to think an application will _not_ be so much faster, and the
applet would be much easier to use (just a URL and you're done!). opinions?
>Still oudeis needs a formulation of its common goal - is that what you
>mean aaron?
i have a definition i'm using a lot when explaining the project to people:
we want to be together, not being together.
it sounds good, and i think it is a good 'central point' for what we are
doing. i reflects our work in progress, and the performance itself. could
this (or something like it) be the 'common goal'?
ooo,
santiago
music is dressed silence
mailto:jaco@overnet.com.ar
http://www.geocities.com/~yaco