With stipulation of the fact that helper methods can be taken too far, what is wrong with something like
Gofer loadSeaside28? Answer: nothing if it hides the details of using the configuration. The problem with the FFI, Seaside, etc. load methods is not that they exist, it is that they use obsolete techniques and/or are broken. One question in my mind is how to replace ScriptLoader class>>loadLatestPackage:fromRepository:. Will Gofer new add:packageName; repository:aRepository; load take care of that? Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Tuesday, January 12, 2010 1:36 PM To: [email protected] Subject: Re: [Pharo-project] Pharo core and Seaside 3.0 On Jan 12, 2010, at 7:25 PM, Lukas Renggli wrote: >> And also the class side install methods of Gofer please. >> >> Lets clean the way for Gofer as downloader/installer, Metacello as >> package management tools. > > These are examples to demonstrate how gofer works. They are not > supposed to be called for loading stuff. > > I am just using them all the time to keep my images up to date :-) :) well this was the same for scriptLoader :) I will pay attention to scriptLoader Stef > > Lukas > > > -- > Lukas Renggli > http://www.lukas-renggli.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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
