Hi Cyril, > I use Seaside 3.1 in Pharo 5 and I have an application running with this > setup currently.
Great! There were indeed very few failing tests that were fixed quickly. I think most of Seaside was just working and you confirm that. > 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. For Seaside 3.1.5, this will remain the case. The tests are fixed and the broken parts have been replaced but the deprecation warning about #subStrings: will not be fixed anymore in Seaside 3.1 For Seaside 3.2, they have been addressed and you should not get any of those anymore. > - In the status component we got a MNU in the VM tab thanks for reporting, will look into that. > - 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). Aha, indeed. The Grease abstraction for this needs to be changed. Will take a look asap. > If I see other problems I will contact you :) Great. You can also report issues on the issue tracker: https://github.com/SeasideSt/Seaside/issues <https://github.com/SeasideSt/Seaside/issues> > > In my baseline I load Seaside3 stable, which is the realise 3.1 I think. Yes, that’s correct. I would suggest using 3.2.0 from now on if you’re not running a production environment though. It’s still a moving target but it’s good if people experiment with it. cheers Johan
