ShoreComponents/Scriptaculous incompatibility

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
12 messages Options
Reply | Threaded
Open this post in threaded view
|

ShoreComponents/Scriptaculous incompatibility

NorbertHartl
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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

ShoreScriptTestComp.st (1K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: ShoreComponents/Scriptaculous incompatibility

Pavel Krivanek-2
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 <[hidden email]> 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
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside





_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: ShoreComponents/Scriptaculous incompatibility

Lukas Renggli
> 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

Are there some conflicts?

Unfortunately Scriptaculous adds quite a lot of extension methods to
WACanvas. The latest published version already has a new factory class
that should collect these methods at a different place. However I
doubt that I will be able to remove those extension methods
immediately as there is a lot of code depending on them.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: ShoreComponents/Scriptaculous incompatibility

Michel Bany
In reply to this post by NorbertHartl
> 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.

Hi Norbert,

As a matter of fact, ShoreComponents modifies the Prototype library,  
therefore ShoreStandardScripts
must be added **after** SULibrary. When you add ShoreStandardScripty  
before SULibrary, you are simply
disabling a ShoreComponents feature (the progress spinner).

However ShoreComponents is assuming an old version of the Prototype  
library and the modification breaks it.

I quickly hacked ShoreComponents-2.6-mb.45. You may want to try it.

Cheers,
Michel.



_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

How serve static files with seaside???

agnaldo4j
Hello

I don't understend how i can serve static files like png, gif, jpg, js,
html whith seaside, some one can help me?

tank's

Agnaldo
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

RE: How serve static files with seaside???

Ramon Leon-5
>
> Hello
>
> I don't understand how I can serve static files like png,
> gif, jpg, js, html with seaside, some one can help me?
>
> tank's
>
> Agnaldo

Though you can serve static files via Seaside, (you'll have to ask someone
else how), you probably shouldn't.  It's fairly standard practice to reverse
proxy Seaside behind Apache and allow Apache to handle that traffic and only
send dynamic requests to Seaside.  How to do so has been discussed many
times in this forum, just search the archives.

Ramon Leon
http://onsmalltalk.com 

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: How serve static files with seaside???

NorbertHartl
In reply to this post by agnaldo4j
On Tue, 2007-01-16 at 13:42 -0200, Agnaldo de Oliveira wrote:
> Hello
>
> I don't understend how i can serve static files like png, gif, jpg, js,
> html whith seaside, some one can help me?
>
You need the Module FileLibrary which you can get from
the Seaside repository on squeaksource.

Open a Monticello Browser. Press the +Repository button in
the upper right. Exchange the URL with
 
http://www.squeaksource.com/Seaside

Select the Entry and press the Open button in the upper right
The fourth topmost entry leads you to the FileLibrary.

Hope it helps.

Norbert

_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: How serve static files with seaside???

Janko Mivšek
In reply to this post by agnaldo4j
Hi Agnaldo,

If you use Swazoo as a web server (on VW), you can use its FileResource
for serving static content.

Agnaldo de Oliveira wrote:

> Hello
>
> I don't understend how i can serve static files like png, gif, jpg, js,
> html whith seaside, some one can help me?
>
> tank's
>
> Agnaldo
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

--
Janko Mivšek
Svetovalec za informatiko
EraNova d.o.o.
Ljubljana, Slovenija
www.eranova.si
tel:  01 514 22 55
faks: 01 514 22 56
gsm: 031 674 565
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

RE: How serve static files with seaside???

Boris Popov, DeepCove Labs (SNN)
... or you could take the (sometimes) unnecessary load away from the framework and let Apache/IIS/etc do what they do best instead. I use in-image resources during development, which get dumped to a directory and Apache takes over when deployed,

http://tinyurl.com/yyc8oz

Cheers,

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Janko Mivšek
Sent: Tuesday, January 16, 2007 8:11 AM
To: The Squeak Enterprise Aubergines Server - general discussion.
Subject: Re: [Seaside] How serve static files with seaside???

Hi Agnaldo,

If you use Swazoo as a web server (on VW), you can use its FileResource
for serving static content.

Agnaldo de Oliveira wrote:

> Hello
>
> I don't understend how i can serve static files like png, gif, jpg, js,
> html whith seaside, some one can help me?
>
> tank's
>
> Agnaldo
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

--
Janko Mivšek
Svetovalec za informatiko
EraNova d.o.o.
Ljubljana, Slovenija
www.eranova.si
tel:  01 514 22 55
faks: 01 514 22 56
gsm: 031 674 565
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: How serve static files with seaside???

Philippe Marschall
In reply to this post by NorbertHartl
2007/1/16, Norbert Hartl <[hidden email]>:

> On Tue, 2007-01-16 at 13:42 -0200, Agnaldo de Oliveira wrote:
> > Hello
> >
> > I don't understend how i can serve static files like png, gif, jpg, js,
> > html whith seaside, some one can help me?
> >
> You need the Module FileLibrary which you can get from
> the Seaside repository on squeaksource.
>
> Open a Monticello Browser. Press the +Repository button in
> the upper right. Exchange the URL with
>
> http://www.squeaksource.com/Seaside
>
> Select the Entry and press the Open button in the upper right
> The fourth topmost entry leads you to the FileLibrary.

FileLibrary is included in both Seaside 2.6 and 2.7

Cheers
Philippe
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: ShoreComponents/Scriptaculous incompatibility

Thomas Koschate-2
In reply to this post by Michel Bany
On 1/16/07, Michel Bany <[hidden email]> wrote:

> I quickly hacked ShoreComponents-2.6-mb.45. You may want to try it.

Michel, where might one find this version?
--
============================================================
Thomas Koschate
[hidden email]
_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Reply | Threaded
Open this post in threaded view
|

Re: ShoreComponents/Scriptaculous incompatibility

Michel Bany

On 20 Jan 2007, at 19:15 , Thomas Koschate wrote:

> On 1/16/07, Michel Bany <[hidden email]> wrote:
>
>> I quickly hacked ShoreComponents-2.6-mb.45. You may want to try it.
>
> Michel, where might one find this version?

See http://www.squeaksource.com/ShoreComponents



_______________________________________________
Seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside