THe key things are I believe.
1) Make sure that VRML code can contain Java applets, rather than a VRML
World *being* a Java Applet.
2) Make sure that VRML can contain Applets from other languages, Java is
not the last-word in languages, and in particular other specialised
languages are going to be much better at handling specific functionality.
3) Figure out the licnsing issues, Java will be useless to us unless the
Applets can be run independantly of which VRML beowser is used,
I believe much of this can be done by means of a suitable API so that the
Java interpreter can communicate with any beowser, as can interpreters for
other languages.
There are three very similar papers that address these issues, those by
Sony, SDSC, and mine (at
http://earth.path.net/mitra/papers/vrml-behaviors.html) (Sorry, I'm offline
at the moment and don't have the other URLs handy.) If we can combine these
we've probably got a good cut at it.
- Mitra
=================================================================
Mitra
[email protected] voice: (415)826-2499 fax: (415)826-4423
<http://earth.path.net/mitra>
Always esmember you're unique, just like everyone else.