Re: Porting from 2.8 to 3.0+

On Wed, Sep 6, 2017 at 6:38 PM, Ramon Leon <[email protected]> wrote:
> Anyone know any good resources, blog posts, or reads out there for porting a
> Seaside 2.8 app to something more modern?  Interested in any lessons learned
> to headaches to expect.  Figure it'd be easiest to go to 3.0 and then once
> stable to 3.1.

Here are the changelogs for 3.1 [1] and 3.2 [2]. Unfortunately we do
not have a changelog for 3.0 :-(

Some of the most breaking changes that come to mind are:

- we don't support #isolate: anymore :-(, you'll have to emulate that
with untracked session/component state
- we don't support setting the timeout for sessions anymore, you'll
have to write a custom session cache for this or register a second
Seaside application
- the Seaside configuration API that is all new

You likely will have to migrate to a new version of whatever dialect
your on, how many headaches that introduces is hard to tell.

The Seaside code has been broken up into multiple modules so you no
longer need to load anything. However that makes loading a bit
trickier. Later versions of Seaside have better Metacello
configurations so maybe you want to switch to those directly.

 [1] https://github.com/SeasideSt/Seaside/wiki/Seaside310Changelog
 [2] https://github.com/SeasideSt/Seaside/wiki/Seaside320Changelog

Cheers
Philippe
_______________________________________________
seaside mailing list
[email protected]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside