I was thinking to move ObjectOut and little friends out of kernel and out them in a dedicated package Then clean MorphObjectOut. There would be nice examples of reflective uses of Smalltalk but I'm not sure that they still work. Now I would do the following: remove BookMorph TabbedPalette SqueakPageCache and see if we can rescue the saving/proxing of Object and Morph Then clean out Project and the other left over from etoy. Stef On Jun 6, 2009, at 3:51 PM, Adrian Lienhard wrote:
When removing SqueakPageCache, shouldn't one remove the whole morph saving logic (i.e., SqueakPage, ObjectOut, MorphObjectOut and maybe more)? I have never used this, so I cannot say whether it may be worth keeping (in which case, we should make it work again).
Adrian
On Jun 6, 2009, at 15:05 , Stéphane Ducasse wrote:
I would be inclined to say that we should remove SqueakPageCache but what the other think? SqueakPageCache is a cache for Morph sved on disc and that can be reloaded Begin forwarded message:
From: codesite-noreply@google.com Date: June 5, 2009 10:53:23 PM CEDT To: stephane.ducasse@gmail.com Subject: Issue 584 in pharo: SqueakPageCache generateURL -> DNU because pathForFile is not defined on ServerFile
Comment #2 on issue 584 by alain.pl...@free.fr: SqueakPageCache generateURL -> DNU because pathForFile is not defined on ServerFile http://code.google.com/p/pharo/issues/detail?id=584
so do we remove SqueakPage (#issue 477) or not ?
-- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project