[Seaside-dev] Relation of Platform Package(s) to Sport Package(s)

[Julian Fitzell]

As you guessed, the Seaside-Sport-Platform package is just an
alternative implementation of the Seaside-Platform base package. I'm
not certain that the Sport platform package is very thoroughly
implemented, though: there are many things we have on our platform
which are not even covered by Sport currently.

I suspect the idea is that you could (if supporting/requiring Sport),
subclass the Sport platform to add stuff for your platform that is not
covered by Sport. Philippe will likely be able to answer in more
detail but unless you see some significant gain by using the
Seaside-Sport-Platform package I would just ignore it and implement
Seaside-Dolphin-Platform - it's pretty basic functionality.

Julian

On Thu, May 7, 2009 at 2:24 PM, Udo Schneider
<Udo.Schneider at homeaddress.de> wrote:
> All,
>
> after doing some work to polish up Dolphin's Unicode Support I (re-)started
> the Seaside Port to Dolphin.
>
> While loading the packages I came accross some Squeak Platform Packages
> (which I'd re-implement for Dolphin) and Sport "Platform" Packages as well.
>
> So what's the relation between these? Do I need to port the Sport packages
> or is this just an alternative "Plafform". Due to the fact that I ported the
> new Sport
> packages anyway to get a recent Swazoo package being based on Sport would be
> no additinal work ... but is it worth it?
>
> Regards,
>
> Udo
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>