Hi, it will require some additional work. I tried to load Monticello to PharoKernel and here are some notes: - some classes still need FileList for the service registration. - initialization order at the end of source files doesn't reflect class hierarchy order - whole class-based initialization problematic, it should be replaced by package-based initialization - we need a general mechanism that will enable to put versioned text files into MC packages (like current source.st), so we will be able to store initialization scripts, general package help etc. - Fonts need some refactorings. Some sort of AbstractFont only with capabilities required only by Text class should be part of the kernel. etc. etc. etc.... :-) Cheers, -- Pavel On Fri, Sep 3, 2010 at 12:50 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
I got an idea: I will ask gabriel to help me producing a metacello config for pharo core and once this is working we can start to work on migrating to use PharoKernel as a basis.
Stef
On Sep 2, 2010, at 11:08 PM, Lukas Renggli wrote:
Very impressive. Can't wait to see Pharo built from such a small image.
Lukas
On 2 September 2010 23:02, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I uploaded the new version of PharoKernel #12121:
https://gforge.inria.fr/frs/download.php/27438/PharoKernel-1.2-12121.zip
The shrinking process is now based on packages.
Cheers -- Pavel
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Lukas Renggli www.lukas-renggli.ch
_______________________________________________ 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