Hi Philippe
sounds quite good to me
>> Thanks for considering this a friendly and positive thread.
>
> So instead of lamenting the state of the world I went ahead and wrote
> some code. To find out what breaks in Seaside I created new packages
> for every Pharo package that didn't work. So I ended up with:
>
> - Grease-Pharo20-Core
> - Grease-Tests-Pharo20-Core
> - Seaside-Pharo20-Core
> - Seaside-Tests-Pharo20-Core
> - Javascript-Pharo20-Core
>
> You can find them in the Seaside 3.1 repository [1]. I'm not really
> sure this was a clever idea but it sounded better than writing a long
> mail.
>
> Things I ran into:
> - file system (obviously)
> - SystemAnnouncer
> - BlockContext is gone
BlockContext has been abandoned some earth cycles ago already :)
> - extension methods are now present on String
> - different Float number printing
this is strange
> File system and SystemAnnouncer are only used by file library.
>
> Right now two tests fail because the GRPackage dependencies are
> inconsistent due to a mix of Pharo and Pharo20 packages. The rest
> seems to work, also functionally.
So this is a good news.
Locked
