Hi Stef,
there are some opened issues so we may start with them: 310 and 311 - the goal is to be able to unload all tests. As Adrian sugested, we may place it the package Tests - at least for now. 346 - easy and safe to integrate 348 - very important issue. Maybe you should place in one update fix for MorphicUIManager>>interactiveParserFor: and in the next the rest of the patch to prevent loading problems There was one wrong step in the development of Pharo during removing of MVC. Pharo deleted all MVC related code however in some cases it was the sign to use the UIManager. 71, 59 - very critical patch but I will have to check if the patches are suitable for the latest pharo
I suggest to remove the unused class variable Current from the ColorTheme (issue 467) firstly - that cleans a lot of obsoleteClasses.
I think that we need one important step in the development of Pharo - the next image that will not contain any code that can be unloaded. That should help us to increase the Pharo quality because now most packges are on the logical level in contradistiction to KernelImage where all packages are standalone unloadable entities. The ideal state is when we have the minimal core image with logical packages (like Collections) and the rest will be all unloadable packages.
Cheers, -- Pavel
On Sun, Mar 1, 2009 at 9:57 AM, stephane ducasse <stephane.ducasse@free.fr> wrote:
The KernelImage ZOO including the building environment is here: http://squeak.cz/public/pub/KernelImage/current/
Of course it is not perfect - the smallest image works only in Linux and MorphicCore needs a lot of fixes so people should start with MorphicExt and so on but it is usable starting point if someone is interested...
-- Pavel
Hi pavel
do you have some fixes, cs list that we could slowly integrate to pharo?
Stef