> On 22 Apr 2015, at 20:22, stepharo <steph...@free.fr> wrote:
>
>
>
> Le 22/4/15 13:23, Esteban Lorenzano a écrit :
>> this is so good.
>> what about integrate it to Pharo?
> No. People should start to think modular.
> No more external tools loaded by default.
> Better invest in "add a startup preference" functionality in the
> configurationBrowser.
>
> Why we do not integrate the excellent tool of baptiste that would show to
> people
> when they are creating package mess? Because of the same reason.
>
But the Pharo that we download should be the Pharo we use.
We tried the other back in Pharo1.0: Do you remember how we fixed with lots
care all details, but then, everyone was using a different image, and all the
details there where not fixed and all work was done double?
If we do not make the Pharo that is downloaded to be that was is used, we will
have
that again.
I don’t want everything in the image, but what everyone is supposed to be using
should
be there without needing an additional step.
Marcus
