[Pharo-dev] why can't we select the browser we want to use anymore via the window menu?

Camille Teruel camille.teruel at gmail.com
Sun Nov 24 15:50:58 EST 2013


On 24 nov. 2013, at 21:44, Marcus Denker <marcus.denker at inria.fr> wrote:

> 
> On 24 Nov 2013, at 21:41, Sven Van Caekenberghe <sven at stfx.eu> wrote:
> 
>> 
>> On 24 Nov 2013, at 21:18, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
>> 
>>> No you should not. 30 is really usable and we are in alpha.
>>> Now removing the old code browser is a goal but we should not fool ourselves. 
>>> Once all the tools are based on Spec, breaking/changing spec will let us without back door.
>> 
>> I don’t consider that a problem, on the contrary: eating your own dog food is good.
>> 
>> BTW, in the past (old tools, old frameworks) the problem was the same.
> 
> When Camille last week tried to convince me to kill the old Compiler *now*
> I said “but it’s so nice to be able to switch when changing the new”.
> He replied: “But there was just one old Compiler, wasn’t there?”
> 
> And he is right.
> 
> What we need to do for real is to support multiple versions of code in the same
> image…

That's work in progress :)

> or multiple images where one can remote-devlope the other. 
> This would solve the problem for real.
> 
> 
> 	Marcus
> 
> 





More information about the Pharo-dev mailing list