[Seaside] ShoreComponents/Scriptaculous incompatibility

[Pavel Krivanek]

Hi Norbert,

I have seen this problem with incompatibility of ShoreComponents and newer
versions of Scriptaculous but I haven't time to find the source of this
problem. But I plan to fix it as soon as possible. Thanks

-- Pavel

On 1/16/07, Norbert Hartl <norbert at hartl.name> wrote:
>
> Hi,
>
> I discovered a problem when using scriptaculous and
> shorecomponents in the same web application. I was
> not able to use the html updater after loading and
> using ShoreComponents. It depends on the order in
> which the libraries are added to the application.
> The conflicting libraries are SULibrary and
> ShoreStandardScripts. Loading ShoreStandardScripts
> first and then SULibrary the updater works. The other
> way round it doesn't.
>
> I'll attach an example app which demonstrates the
> problem. It registers the app at two entry points
> with different library order. One is working the
> other isn't.
>
> I'm using
>
> Seaside 2.7a1-pmm.153
> Scriptaculous-lr.165
> ShoreComponents-2.6-mb.44
>
> Norbert
>
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070116/3ca682d1/attachment.htm