Sorry, too many counter-examples.  The situation has improved with time, but overall, it's a complicated mess with instructions that change almost weekly.  Just being honest.


From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Guillermo Polito [guillermopolito@gmail.com]
Sent: Friday, April 27, 2012 12:26 PM
To: Pharo-project@lists.gforge.inria.fr
Subject: Re: [Pharo-project] What about making the configuration browser more visible?

Wat?  Probably there was a misunderstood...

1) if you are an user of the project, stable should be enough and fine.
2) if your project is coupled to the project, probably you are coupled to an specific version.  Thus, in your configuration you better put the specific number :).
3) if your project is not coupled to the project, just inteded to load it, using stable should be enough and fine.

Example of 2) is you loading OmniBrowser or Nautilus.
Example of 3) is your project using a specific version of XmlSupport or seaside.
Example of 4) is the ImageBuilder of Mariano, which loads a lot of stuff to build a Development image.

Guille

On Fri, Apr 27, 2012 at 5:06 PM, Schwab,Wilhelm K <bschwab@anest.ufl.edu> wrote:
Put another way, if it's that simple, why all the contrary instructions over time?


________________________________________
From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Camillo Bruni [camillobruni@gmail.com]
Sent: Thursday, April 26, 2012 7:40 PM
To: Pharo-project@lists.gforge.inria.fr
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: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of St�phane Ducasse [stephane.ducasse@inria.fr]
> Sent: Thursday, April 26, 2012 6:17 PM
> To: Pharo-project@lists.gforge.inria.fr
> 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