In Dolphin, one can cope with that fairly easily - most of the time. The trick is to change the affected class' serializing version number, which causes the loader to seek help reading old serialized data, which arrives as an array. Streams work well for adapting the old array into an array that is correct for the current version.
I have not used SIXX long enough to encounter this in a significant way. SIXX appears to depend on messages/apsects, where Dolphin's serializer deals directly in instance variables. My guess is that SIXX will be tolerant of changes that would clobber Dolphin's serializer, but that Dolphin provides tools to handle it. SIXX has something too; I have not needed it yet. One thing about SmartReferenceStream: the conversion methods go in the serializer itself; they belong in the affected class, or in its proxy if one is used. SmartReferenceStream also assumes that user==developer :( Bill ________________________________________ From: pharo-project-boun...@lists.gforge.inria.fr [pharo-project-boun...@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse [stephane.duca...@inria.fr] Sent: Monday, February 14, 2011 3:41 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] A new GUI visual designer What is happening if the class of your application UI gets a new variables or if a superclass changes its structure? May be in objective-C you have to resave your nib? Stef DynaBook.
