It could be done that way. But, for this feature and others, we decided to implement it as a utility first. This was to make sure everything worked well. We could eventually fold it back into the core as a speciallized implementation of serialization. But, the current way of doing it gives us a bit more flexibility in defining its behavior and characteristics.
Doug Twilleager Java 3D Team Sun Microsystems >Subject: [JAVA3D] SceneGraphIO - why not serialization ? >To: [EMAIL PROTECTED] >MIME-version: 1.0 >Content-transfer-encoding: 7bit >X-Accept-Language: en-us, en >Delivered-to: [EMAIL PROTECTED] >User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9) Gecko/20020311 > >I have just read short docs about SceneGraphIO (j3d format). I >understand stuff with create/resolve references, but why just normal >serialization is not used ? > >Wouldn't it be easier to use serialization and manually serialize tricky >fields and add some post-serialization hooks to initialize needed native >resources (if they are needed at all) ? > >Artur > >=========================================================================== >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". =========================================================================== 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".
