[Seaside] Pharo 2.0 scriptaculous does not work
johan at inceptive.be
Fri Jun 7 14:43:03 UTC 2013
I'm adapting the Seaside config to include that group instead of the Zinc-Seaside package.
On 07 Jun 2013, at 14:17, Sven Van Caekenberghe <sven at stfx.eu> wrote:
> On 07 Jun 2013, at 10:11, Johan Brichau <johan at inceptive.be> wrote:
>> On 07 Jun 2013, at 10:03, Sven Van Caekenberghe <sven at stfx.eu> wrote:
>>> 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.
>> If I am correct, that should not be a problem.
>> The Seaside30 config can specify to load the 'Zinc-Seaside' version as specified by the Zinc config.
>> All you have to do is list the Zinc-Seaside package in your version methods and make sure that it does not get loaded when not explicitly asking for it.
>> I believe that can be done by not putting it in the #default load group.
> I just created ConfigurationOfZincHTTPComponents-SvenVanCaekenberghe.49 which now has a 'Seaside' group that loads the 'Zinc-Seaside' adaptor package with a specific version. It is of course not loaded by default.
>> If you want your config to be complete, you can list a dependency on the Seaside project for the Zinc-Seaside package. This would only be loaded if somebody explicitly load the Zinc-Seaside package.
> For now I skipped the dependency on Seaside, we'll see how it goes.
>> If that does not work, we need to ask the Metacello doctor ;-)
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> Sven Van Caekenberghe
> Proudly supporting Pharo
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside