2009/7/21 nullPointer <[email protected]>: > > 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. > Just a guess: maybe it is better to persist a morph(s) as is - as original objects - just keep them somewhere in classvars. Then to create a new view of it, just do a #deepCopy.
P.S. counter asString don't needs to be enclosed in parenthesis. > 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 > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
