On Feb 21, 2010, at 4:44 PM, Adrian Lienhard wrote:
> On Feb 21, 2010, at 11:59 , Stéphane Ducasse wrote:
>
>> Marcus this is strange we removed a lot of code and the image size grows :)
>
>> We will have to investigate that.
>
>
> Did you run the cleanUpFor* methods? The grow may be due to MC cached definitions. Or to the ScriptLoader log.
>
MC cache is delete after each update. But the cleanup methods need to be run, yes... changesets hold on to old methods, making
changeset history quite expensive.
I actually think the main problem is the Scriptloader... it gets big quite quickly (both in terms of generated code and the log).
>
>>
>> I would like also to play with mariano about the idea of use metacello to manage the unstable + external but pharo manage packages. To see how far we can unload packages now that settings, ....
>
> Indeed, that would be cool. Extracting ImageSegment into an external package also is on my todo list.
good!
--
Marcus Denker --
http://www.marcusdenker.deINRIA Lille -- Nord Europe. Team RMoD.
_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Locked
