[Seaside] Pharo 2.0 scriptaculous does not work
diego.lont at delware.nl
Mon Jun 10 07:23:16 UTC 2013
Let me try to understand what you want.
You want to move Zinc-Seaside to Zinc, and thus build Zinc depend on Seaside instead of the other way around.
So you want to add a group to Zinc, called 'Seaside', that loads Zinc-Seaside that requires Seaside30, so it loads after Seaside30 config is loaded with Seaside-Core.
Both projects have load type linear, so it should work …. but my guess is that you than have to remove Zinc from Seaside altogether.
So I think my question would be: why should Seaside still depend on Zinc, when you move Zinc-Seaside to Zinc?
On Jun 8, 2013, at 10:11 AM, Johan Brichau wrote:
> I think I need the metacello doctor to work out what I had in mind.
> Dale? you there? :-)
> In the meantime, I bumped a new version that references the correct Zinc-Seaside package version, such that it works correctly for now.
> The problem I have is that Metacello does not support the #requires: condition for project references. Before loading Zinc (with Zinc-Seaside), the Seaside-Core package needs to be loaded.
> I was under the false impression that such a statement was possible in Metacello, but alas... I am wrong.
> So now I need to figure out how we can:
> - let the Zinc-Seaside package version be controlled by the Zinc project (it makes more sense)
> - have the Seaside config reference the Zinc project but only load it after having loaded Seaside-Core.
> I tried several things yesterday including referencing Seaside from Zinc as well, but that went into an infinite loop (metacello does not detect loops?).
> Guess I was a bit too bold yesterday, but maybe Dale can shed some light on how to accomplish the above two items?
> On 07 Jun 2013, at 16:43, Johan Brichau <johan at inceptive.be> wrote:
>> Thanks Sven.
>> 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
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside