> > We need named objects. These are the hooks that a movement language would
> > have to use to 'enact' a .wrl file.
>
> you should be able to use DEF to give an object a name
>
> DEF objectname objectype { fields children}
>
> and the keyword USE to use that object again
>
> and so you could define an object and then use USE and
> transform to move that object... but there is no way
> to specify that you have to move it at exactly time x
> like you'd want to with a scientific visualization
>
> and with the discussion of common libraries how about
> a viariation of USE that says use this object if you
> know what it is, else you can get it at this URL
> something like:
>
> Transform { translation 0 2 0}
> USE {WWInline {name "teapot.wrl"} }
> teapot
>
> which says move the teapot 2 (up?) if you don't know what teapot is
> load teapot.wrl
OK, This is how you do it from within the language, and from this and
other posts I understand that objects can have names. I assume then, that
at the browser end, a good browser can load a starting point file,
display it, and wait for a connection which will send scraps of VRML text
which causes the names objects to move, or change.
How about the server end? Is there a way I can specify in a .wrl file
that whoever gets the file is also expected to leave a socket open for my
server to connect to and send updates. I realize this is mostly a server
function, and outside the current VRML spec, but I think a hook may be
needed here. How is the user's browser to tel the difference between a
static .wrl file, and one that is only a starting point for an animation
which my server is about to send? Without some sort of tag, the browser
may not be listening to its socket for the updates to come in.
Maybe we need to define the file type .awl, for Animated World. (I like to
stick to three letter extensions, so we don't confound the DOS users.:)
Such a file would be a clue to the browser that it should be ready for
server updates, or the updates are included in a special section that
contains animation information. The latter format would allow short
animations to be sent in one reply without further server involvement.
---
Andrew C. Esh mailto:[email protected]
Computer Network Technology [email protected] (finger for PGP key)
6500 Wedgwood Road 612.550.8000 (main)
Maple Grove MN 55311 612.550.8229 (direct)
<A HREF="http://www.mtn.org/~andrewes">ACE Home Page</A>