Doug Twilleager wrote: > 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.
Yes, but on the other hand it makes user-defined classes harder to serialize. For example I have map of transform group links (string->tg) in my behavior. Currently I have to manually iterate the map, putting string and integer for each entry and then the same reading it back. With serialization it would work out of box. Ok, but I understand that integrating it into core would be tricky. After all it is not much work to write few interators... :) 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".
