On 4 March 2011 14:55, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
On Fri, Mar 4, 2011 at 2:43 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
On Fri, Mar 4, 2011 at 2:36 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
On Fri, Mar 4, 2011 at 2:26 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
On Mar 4, 2011, at 2:24 PM, Pavel Krivanek wrote:
Great!
does it have the same code base as the current Pharo-Kernel?
Yes. 1.3 latest Core. (I am just integrating the printon fix)
    Marcus
So if we will be able to run startup scripts in this image, we be able to use the Pharo-Kernel scripts for loading all the content of the PharoCore back. Perfect!
-- Pavel
Hmm, Pharo-Kernel has 475 classes and traits and similar size (2.2 MB).
-- Pavel
I see, the base content of this image is defined as:
(each category beginsWith: 'Kernel') or: [(each category beginsWith: 'Collection') or: [(each category = 'Exceptions-Kernel') or: [(each category = 'Announcements-Core') or: [(each category = 'System-Pools') or: [(each category = 'System-Support') or: [(each name == #EncodedCharSet) or: [(each category == 'Multilingual-Encodings') or: [(each category == 'Multilingual-Languages') or: [(each name) == #Unicode]]]]]]]]]].
That is really radical shrinking :-) But it has great potential. I'll try to play with it...
Probably there are a lot of junk inside, because the algorithm for picking which objects are to go into image is quite simplistic. And that's the actual aim of this project - invent ways how to tell/identify objects which we want to see in kernel image, otherwise just replace it with dummy or halt tracing, asking a developer to fix unwanted reference.
-- Pavel
-- Best regards, Igor Stasenko AKA sig.