Andrew,
I have recently subscribed to the list as I am hoping to produce an editor
for J3D for the final year project of my Visualisation degree.
I have been reading with interest the current debate regarding the pluses
and minuses of J3D and in particular your comments about the serialization
of classes to store scene graphs:
>I'm in danger of digressing here, so I'll return to the original point:
>serialization is Java's ace-in-the-hole. Serialization of Java3D objects
>is easy to implement (we build everything in 3DSMax but once tweaked in
>our J3D editor we serialize it out, be it a humble lonely sphere or a
>large scene graph). Java3D does not directly support serialization
>however so you have to do it through the back door, and by using
>placeholder classes instead of extending Java3D classes. This is a big
>weakness in my opinion, and one which I hope will be addressed in a
>future release.
At present (perhaps naively) this is the area of developing the editor which
I foresee causing me most difficulty, although this may say more about my
knowledge of serializing Java classes than the ease of the rest of the
development work. Any insight you can give me into how you have used your
placeholder classes, or pointers to places to read up about the topic would
be greatly appreciated.
Thank you
Andy Wilkinson
===========================================================================
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".
