[Seaside-dev] WAVirtualMachineStatus>>#renderValuesOn:

[Esteban Lorenzano]

On 16 Feb 2014, at 23:20, Philippe Marschall <philippe.marschall at gmail.com> wrote:

> On Sun, Feb 16, 2014 at 2:38 PM, Johan Brichau <johan at inceptive.be> wrote:
>> 
>> On 16 Feb 2014, at 14:07, Sven Van Caekenberghe <sven at stfx.eu> wrote:
>> 
>> This not an incompatibility between Pharo 2 and 3. Instead of creating a new
>> package, it could also be fixed with a little dynamic hack.
>> 
>> 
>> Though I’m always amazed that deprecated methods immediately break things in
>> Pharo.
>> They’re supposed to keep working until the next version, but the ‘raise a
>> blocking dialog’ setting that is on by default in Pharo makes it break
>> immediately.
> 
> Well we can fix that [1]
> 
> [1] http://code.google.com/p/seaside/issues/detail?id=781

there is also a setting in Pharo to disable the blocking dialog. 

Deprecation raiseWarning: false.

Esteban

> 
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev