Ffenestri is a possible route to host windows.  I am *not* a "native widgets or 
bust guy" (emulation has its points, performance under scaling being high on 
the list), but there are reasons to want to use host windows too.  I would 
hesitate to remove this too quickly, unless Pinesoft tells us there is a better 
way to meet the objective.

Compression probably does not need to be in the kernel, but IMHO it does belong 
in Pharo 1.0.  Ditto sounds.  Sound is something that people will expect in a 
well-rounded system.

I'm all for cleaning out cruft, but things that are part of the releases are 
probably more likely to get seen, used, and therefore have bugs detected.  

Bill


-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Adrian 
Lienhard
Sent: Monday, March 16, 2009 4:21 PM
To: Pharo Development
Subject: [Pharo-project] Removing more classes from Pharo

In quest of modularizing Pharo and reducing its memory footprint, I  
was wondering whether the following packages should be removed:

- TrueType and related classes in Multilingual-Display (are obsolete  
since we have FreeType, no?)
- Services (does not seem to be used, except by a subclass in Polymorph)
- Graphics-External-Ffenestri (why is this in the image??)
- Compression (I think, does not need to be in the kernel)
- Sound (dito)
- Traits-LocalSends and Traits-Requires (are not used)
- MorphicExtras (I assume at least some of those could extracted)
- ...?

I would put these in a repository so they can be loaded if needed. The  
extraction of some of these packages likely needs some work, but would  
be a first step towards a more modular kernel.

What do others think?

Adrian

___________________
http://www.adrian-lienhard.ch/


_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to