Le 20/03/2016 19:49, Johan Brichau a écrit :
Hi Pharoers,
If you are looking to use Seaside in Pharo 5, please go ahead and let us know if you run into any issues. Seaside 3.1.5 and 3.2.0 (unreleased) load into Pharo 5 and all tests are green [1].
Hi, I use Seaside 3.1 in Pharo 5 and I have an application running with this setup currently. I thought about sending a mail to the seaside mailing list soon but if you ask I will respond here :) This is the main issues I got the past few weeks: - When we load Seaside of Pharo 5 we have to add "onWarningLog" in order to avoid a lot of deprecation warning. - When we register a component to WAAdmin we also have a deprecation warning. - In the status component we got a MNU in the VM tab - In the latest Pharo5 the seaside adaptor is not launched by default on 8080. We have to add it manually (probably because of the SessionManager changes). If I see other problems I will contact you :) In my baseline I load Seaside3 stable, which is the realise 3.1 I think.
Also: I know the finalization of 3.2.0 is long overdue, so news about that is coming soon.
cheers, Johan
[1] https://ci.inria.fr/pharo-contribution/job/Seaside/
âLoad release 3.1" Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #'release3.1'; load.
âLoad pre-release 3.2" Metacello new configuration: 'Seaside3'; repository: 'http://www.smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main'; version: #â3.2.0'; load
-- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France