Thanks for this Noury.  The interface building side of Morphic needs this kind of thing.

On the matter of serialisation, as alternative it would be nice (also) to be able to generate the objects from code but I don't think this is very easy.  Morphic is inconsistent between how coding works and how scripting works. (E.g. a morph responds to a forward: command in scripting but coding it involves messing around with (assuring) costumes - also the naming of components doesn't link to variable names very conveniently.)  An alternative to byte serialisation could be to generate full Smalltalk initialization code that can build the object fully from scratch - does this sort of code exist?

Yours

Bob