On Dec 22, 2008, at 17:47 , Keith Hodges wrote: > Bill Schwab wrote: >> It makes a lot of sense to use MC, universes, etc. rather than re- >> write >> them; no argument there. Would it help to roll ScriptLoader into >> Installer? > Installer works for all commonly used Squeak images, so you would > need a > ScriptLoader for each image that people are using. > > Coincidentally that is almost exactly the way Sake/Packages already > works, except that it is aware of dependencies and can sort a list of > items that it is asked to load in order to honour dependencies. The > functions that ScriptLoader performs should really be rolled into the > Packages-Library class PacakgesPharo01, for Sake/Packages which is a > repository of "scripts" for loading things (most definitions simply > supply a url rather than a script).
uh, sure? The main purpose of ScriptLoader is to support the generation of new updates. I recently implemented support for almost the complete process from detecting new changes, simulate the update for testing, pushing changes to SqueakSource and generating the scripts and cs files for the update stream. People started adding #loadOB methods on the class side of ScriptLoader -- I guess, these may be better handled by Sake/Packages. Adrian _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
