This is just when you load a newer version of SmallWiki 2 into the current development version. Please note that the development versions are not always backward compatible and that in some cases (like this one) you need to reinitialize your model. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Your fix is a bit strange, because not all instances of a link want to be embedded. This will certainly lead to problems as soon as the renderer takes care about this new property. It is probably better to use false as a default instance, but then it will break the environment. So if you really don't want to drop your existing model instances and migrate to the latest version I suggest to do something along the lines: SW2Link allSubInstancesDo: [ :e | e instVarNamed: 'embedded' put: false ]. SW2SeasideFrame initializeEnvironment. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Damien Most of the time, I would suggest to drop the existing instances, but this is a nice examples of how we can keep a system running two years and upgrade it on the fly. When you have to do this kind of things this is quite powerful. Stef

You open an inspector on SW2Kernel instances and remove your the old kernels from the ordered-collection. Then you evaluate SW2SeasideFrame initialize that will setup a new Seaside application and ask you if it should create a new kernel, since you deleted the old ones. Cheers, Lukas

Normally this should be based on a GC if you do not have a root structure somewhere. You can also nil out some instance variables and do a GC SmalltalkImage or Smalltalk garbage.... stef On 11 juil. 05, at 18:04, Damien Cassou wrote: