Why don't you a kind of literalArray syntax like in VW. Declarative syntax for saving description are the way to go. I would not serialize the composite. You could use mse for example: there are loader and saver for mse in the Fame package I guess. Stef
Excuse me for my poor english.
I´m developing a GUI Builder for Pharo -> http://www.youtube.com/watch?v=CHbc1t83fEI
One of my problems is the way of persist a morph.Now i use the same way for create a Morph than message #saveOnFile but not saving in a external file else in array of bytes returned for a #spec message.
I would know if morphic allow or exists another way of persistence more readable and fast. A complex morph serialized of that way is too slow in load.
Regards. -- View this message in context: http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3292117.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project