Paul Byrne wrote:
> If the Node.useData object is serializable then it will be serialized to the
> output file using standard java.io.Serialization.
OK, so if we don't implement the serialisation interfaces then we should
not have to worry about it writing data out that it shouldn't. The
problem then will be that people might load a VRML scenegraph, attempt
to write it out with j3f and wonder why when it loads back in nothing
works as it did before.
Oh well, too bad, it's something they really shouldn't be doing in the
first place anyway. Even if we did serialise it, I can't see it working
for our loader anyway - there are so many extra concepts that need to be
used in the runtime support that we could never dream of supporting that
sort of capability anyway.
The joys of working with a high-level message driven scenegraph.....
--
Justin Couch http://www.vlc.com.au/~justin/
Freelance Java Consultant http://www.yumetech.com/
Author, Java 3D FAQ Maintainer http://www.j3d.org/
-------------------------------------------------------------------
"Humanism is dead. Animals think, feel; so do machines now.
Neither man nor woman is the measure of all things. Every organism
processes data according to its domain, its environment; you, with
all your brains, would be useless in a mouse's universe..."
- Greg Bear, Slant
-------------------------------------------------------------------
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
