I've only ever worked with Sound, and when I didn't know how to do much with packages and had to make changes to the Sound package I just saved the whole thing loaded it into a new image, so I think it should be relatively straightforward to do as you suggest.
However, if the Polymorph "sound" theme became part of the standard Pharo image, you would need sound, but that's the only thing I have heard people talking about. Umm...probably right with TrueType. Morphic, it seems, you just never know what it might interfere with! The rest I don't really know anything about. Then, maybe you could just publish them via any of the standard options (Universes, etc...) with a standard naming convention? Like Pharo-Sound...etc? Take care, Rob On Mon, Mar 16, 2009 at 5:21 PM, Adrian Lienhard <[email protected]> wrote: > 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
