[Seaside] Pharo 2.0 scriptaculous does not work
Sven Van Caekenberghe
sven at stfx.eu
Fri Jun 7 08:03:12 UTC 2013
On 07 Jun 2013, at 09:56, Johan Brichau <johan at inceptive.be> wrote:
> Hi Sven,
> On 07 Jun 2013, at 09:37, Sven Van Caekenberghe <sven at stfx.eu> wrote:
>> Now, ConfigurationOfZincHTTPComponents does _not_ specify which version of Zinc-Seaside should be loaded. It is not even in the config. It is Seaside that depends on Zinc and the adaptor, the other way around in not possible. It seems that somehow, the latest Zinc was loaded and not the latest adaptor, which matches it.
> Seaside depends on the #stable version of Zinc but if Zinc upgrades its #stable version, the Seaside config should also upgrade its matching version of Zinc-Seaside.
> Therefore, it seems natural that Zinc specifies the Zinc-Seaside version number that matches the Zinc version (as you say).
I am willing to do that (it sounds logical), but can that be done without depending on Seaside itself ? Because that does not sound practical, maybe reducing a circular dependency or at least an interference with the specific Seaside versions and groups that you initially want to load.
> In earlier versions of Zinc, the Zinc-Seaside package was mentioned (version 1.0 and 1.1).
> Or we adapt the Seaside config to depend on a specific Zinc version (which is less optimal imho)
> What do you think?
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside