[Seaside-dev] Current working combination of Packages

[Philippe Marschall]

2008/11/24 Udo Schneider <Udo.Schneider at homeaddress.de>:
> Philippe Marschall schrieb:
>>
>> Are we talking about Swazoo 1 or Swazoo 2? The latest script I posted
>> in the announcement thread should load Swazoo 2 and have it working.
>>
>
> The whole stuff is based on the newest Swazoo beta (2.2 Beta1) - I ported
> this already together with SPort.
>
>> The specific packages are Seaside-Swazoo and Seaside-Adaptors-Swazoo.
>> You probably don't need DynamicBindings, KomServices,
>> Seaside-Adaptors-Comanche and Seaside-Tests-Adaptors-Comanche as these
>> are Kom related.
>>
>
> That's where my problem starts. Which version of
> Seaside-Swazoo/Seaside-Adapters-Swazoo in which Repository should I take?

Latest Seaside-Adapters-Swazoo from MIT repository. It can only be
found there and that's the location the script uses.

Latest Seaside-Swazoo from LGPL repository. It can only be found there
and that's the location the script uses.

Check also:
http://code.google.com/p/seaside/wiki/LoadOrder

>> General note on porting Seaside 2.9:
>> - All the packages that do not have a -Squeak- in the package name
>> should be loadable unchanged. If you have to change them that's a bug.
>> Please report it.
>>
>
> I'll check it. I think I changed some exception handler stuff as Dolphin
> forces a one argument Block in #on:do:. I'll check.

We should have fixed those. Maybe not in the version in the script but
it should be fixed in the latest code. In general each package should
have an associated repository and you can load the latest version from
there.

>> - All the packages that do have a -Squeak- in the package name might
>> need to be ported. You can either reimplement them or change them. If
>> you decide to change them consider developing them in Squeak and then
>> loading them unchanged into Dolphin. This should make it easier for
>> you to keep in sync with upstream changes because you can simply merge
>> using Monticello.
>>
>
> This might be a problem as some Dolphin specific classes are missing in
> Squeak.

You could create a Dolphin-Mock package that provides these classes.
They don't even need to have methods, because you only need the global
symbols to be able to compile the code. There exists such a thing for
the RC GemStone collection clases.

> However I do fully agree to keep everything in sync with the main
> development stream. If I change something in Dolphin which is not Dolphin
> specific I'll move it over to Squeak/Monticello as well.

Cheers
Philippe