In the past, that hasn't been universal. More recently, I was told to *always* load specific versions; never use the symbolic versions. We have to get our story straight on this.
________________________________________ From: [email protected] [[email protected]] on behalf of Camillo Bruni [[email protected]] Sent: Thursday, April 26, 2012 7:40 PM To: [email protected] Subject: Re: [Pharo-project] What about making the configuration browser more visible? On 2012-04-27, at 01:17, Schwab,Wilhelm K wrote: > Can they really download stuff? How much? Until the configurations are > truly self-describing and "know" what to use for which version of Pharo[*], > the Config Browser is really (sorry guys) a very clear illustration of what > we have yet to do in the way of packaging. > > Bill > > [*] there needs to be one incantation that works to load everything, > something like #loadStable. Then a config browser can work as advertised, > and I fear, not until. Prove me wrong :) seems like you missed something (Metacello Configurations)? it's done like this in st-code: ConfigurationOfXYZ project load: #stable > ________________________________________ > From: [email protected] > [[email protected]] on behalf of Stéphane Ducasse > [[email protected]] > Sent: Thursday, April 26, 2012 6:17 PM > To: [email protected] > Subject: Re: [Pharo-project] What about making the configuration browser > more visible? > > Ok for me. > Package Maps Loader > > Stef > >> What about naming it "Package Loader" or "Package center" or something like >> that? >> And putting it in the main menu instead of inside of Tools? >> >> I want people who open pharo for the first time to say "Hey, here I can >> download stuff!!!" >> >> Guille
