[Seaside-dev] implementation classes and initialization

[Philippe Marschall]

Hi

One of the main consequences of breaking Seaside into modules is that
SeasidePlatformSupport does no longer include the implementation.
Instead it delegates to an implementation that will be provided later
by an other package. An important consequence of this is that during
the initialization of the Seaside-Core package the implementation is
not yet present. This means you can't automatically register
components in the Seaside-Core package in the #initialize method on
the class side. I moved this code to #initializeClass methods which I
send during the initialization of the Seaside-Squeak-Core package.

Some clarification about the Seaside-Sport-Core package:
The idea is not that we move Seaside to SPort and for example replace
the chronology classes with their SPort equivalents. Instead it is
only a partial implementation of SeasidePlatformSupport using SPort.
It is not a full implementation because SPort does not provide all the
functionality we need. The target audience for this is not existing
ports but new ports that already have SPort. This reduces the amount
of implementation code they have to write. Existing ports are of
course free to move to SPort if they want to.

Cheers
Philippe