Hello all,
I've finally decided to take the plunge and use Scriptaculous for some UI, stuff, mostly due to Ramon's blog :) (I've been using seaside for several years and have built a number of apps with it, but not for a while).... Anyway, I have loaded Seaside2.6b1-mb.105 and Scriptaculous-lr.143 but when I try using anything, like the updater, I get an error message on the browser: Ajax variable not found. I must be missing something :) Brian _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Brian Brown wrote:
> Hello all, > > I've finally decided to take the plunge and use Scriptaculous for some > UI, stuff, mostly due to Ramon's blog :) > > > (I've been using seaside for several years and have built a number of > apps with it, but not for a while).... > > Anyway, I have loaded Seaside2.6b1-mb.105 and Scriptaculous-lr.143 > > but when I try using anything, like the updater, I get an error > message on the browser: > > Ajax variable not found. > > I must be missing something :) > > Brian > 1) Is the useScriptaculous setting set to true in the application config 2) You need to add SULibrary to your application's libraries 3) If you look at the history in monticello for lr-143 there is some mention of it being made to work with Seaside2.7a, which made me suspicious that that particular version might not work with 2.6b, so I went for Scriptaculous.pmm-138 instead. Keith Send instant messages to your online friends http://uk.messenger.yahoo.com _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Brian Brown-2
> Anyway, I have loaded Seaside2.6b1-mb.105 and Scriptaculous-lr.143
Careful! Scriptaculous-lr.143 and 142 require Seaside from the 2.7a1 branch. lr.141 should work. HTH Michel. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by keith1y
On Oct 19, 2006, at 10:09 AM, Keith Hodges wrote: > > 2) You need to add SULibrary to your application's libraries That did it, thanks Keith! _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Bany, Michel
Alright, I'll load the 141 code, but my test is currently working ;)
- Brian On Oct 19, 2006, at 10:12 AM, Bany, Michel wrote: >> Anyway, I have loaded Seaside2.6b1-mb.105 and Scriptaculous-lr.143 > > Careful! Scriptaculous-lr.143 and 142 require Seaside from the 2.7a1 > branch. > > lr.141 should work. > > HTH > Michel. > _______________________________________________ > 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 |
In reply to this post by keith1y
> 1) Is the useScriptaculous setting set to true
> in the application config This is just Pier that uses this setting. > 2) You need to add SULibrary to your application's libraries This is the most common problem indeed ;-) > 3) If you look at the history in monticello for lr-143 there is some > mention of it being made to work with Seaside2.7a, which made me > suspicious that that particular version might not work with 2.6b, so I > went for Scriptaculous.pmm-138 instead. Yes the latest version only works with the 2.7 branch. If you are using an older version of Seaside you need to go backwards trough the commit comments to see where it says "from now on only Seaside2.7a". Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Bany, Michel
Michel,
Does this mean that going forward I'd have to look at jumping my production code over to the 2.7a branch if I want to stay up to date with Scriptaculous? Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [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 Bany, Michel Sent: Thursday, October 19, 2006 9:12 AM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: RE: [Seaside] Scriptaculous > Anyway, I have loaded Seaside2.6b1-mb.105 and Scriptaculous-lr.143 Careful! Scriptaculous-lr.143 and 142 require Seaside from the 2.7a1 branch. lr.141 should work. HTH Michel. _______________________________________________ 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 |
> Does this mean that going forward I'd have to look at jumping my
> production code over to the 2.7a branch if I want to stay up to date > with Scriptaculous? There is not much different in the latest version of Scriptaculous. The library itself is pretty stable right now and there are no new features coming from the JavaScript side. So it is not really necessary to update right now, maybe it is the best to wait a little bit, after all Seaside 2.7a is a moving target ... Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
What's the timeline on 2.7a anyway? I know some people are working on
it, but so far I have no idea who and what direction its taking even. We'd placed some serious long run bets on Seaside, so any feedback would be greatly appreciated. Thanks! -Boris -- +1.604.689.0322 DeepCove Labs Ltd. 4th floor 595 Howe Street Vancouver, Canada V6C 2T5 [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 Lukas Renggli Sent: Thursday, October 19, 2006 2:36 PM To: The Squeak Enterprise Aubergines Server - general discussion. Subject: Re: RE: [Seaside] Scriptaculous > Does this mean that going forward I'd have to look at jumping my > production code over to the 2.7a branch if I want to stay up to date > with Scriptaculous? There is not much different in the latest version of Scriptaculous. The library itself is pretty stable right now and there are no new features coming from the JavaScript side. So it is not really necessary to update right now, maybe it is the best to wait a little bit, after all Seaside 2.7a is a moving target ... Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ 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 |
> What's the timeline on 2.7a anyway? I know some people are working on
> it, but so far I have no idea who and what direction its taking even. > We'd placed some serious long run bets on Seaside, so any feedback would > be greatly appreciated. Philippe and I started this version at ESUG. One of the main goals was to old renderer deprecated and to clean up the old code, if necessary by explicitly breaking backward compatibility. There are some ugly parts that we would like fixed and that annoy us every day: - clean up the source code, e.g. remove old assignments (done) - default #rendererClass changed, most components converted (mostly done) - several fixes to rendering canvas (mostly done) - #updateRoot: to use a canvas like API (done) - to have a file library in Seaside (done, but not integrated) - to clean up WARequestHandler and friends (open) - clean up the code using SLint (started) - deprecate unused and old unused code (started) Philippe? I am sure that I forgot a lot of things! For the timeline: Things just happen as we need them and as we have time to work on (for me this is very limited at the moment). We are using this version in several open-source and commercial projects. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2006/10/20, Lukas Renggli <[hidden email]>:
> > What's the timeline on 2.7a anyway? I know some people are working on > > it, but so far I have no idea who and what direction its taking even. > > We'd placed some serious long run bets on Seaside, so any feedback would > > be greatly appreciated. > > Philippe and I started this version at ESUG. One of the main goals was > to old renderer deprecated and to clean up the old code, if necessary > by explicitly breaking backward compatibility. > > There are some ugly parts that we would like fixed and that annoy us every day: > > - clean up the source code, e.g. remove old assignments (done) > - default #rendererClass changed, most components converted (mostly done) > - several fixes to rendering canvas (mostly done) > - #updateRoot: to use a canvas like API (done) > - to have a file library in Seaside (done, but not integrated) > - to clean up WARequestHandler and friends (open) > - clean up the code using SLint (started) > - deprecate unused and old unused code (started) > > Philippe? I am sure that I forgot a lot of things! - make the root api more canvas like (first version done, we are trying how it works, first results are positive) - new very cool deprication mechanism - full ruby support (backported to 2.6b1) - even more html elements (backported to 2.6b1) - WAAnchorTag >> #tooltip has been removed (use #title instead) - WAListener fixes (backported to 2.6b1) - other fixes and convenience methods > For the timeline: Things just happen as we need them and as we have > time to work on (for me this is very limited at the moment). > > We are using this version in several open-source and commercial projects. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > 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 |
In reply to this post by Brian Brown-2
> Michel,
> > Does this mean that going forward I'd have to look at jumping > my production code over to the 2.7a branch if I want to stay > up to date with Scriptaculous? Hi Boris, I already tried the port of 2.7a to VW, but did not publish it because I would like to check how it fits with the other components (SeasideAsync, SeasideTesting, etc.). I may also explore another possibility: retrofiting what is needed by Scriptaculous into 2.6b1. Just a matter of time... Michel. _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Philippe Marschall
On 10/20/06, Philippe Marschall <[hidden email]> wrote:
> 2006/10/20, Lukas Renggli <[hidden email]>: > > > What's the timeline on 2.7a anyway? I know some people are working on > > > it, but so far I have no idea who and what direction its taking even. > > > We'd placed some serious long run bets on Seaside, so any feedback would > > > be greatly appreciated. > > > > Philippe and I started this version at ESUG. One of the main goals was > > to old renderer deprecated and to clean up the old code, if necessary > > by explicitly breaking backward compatibility. > > > > There are some ugly parts that we would like fixed and that annoy us every day: > > > > - clean up the source code, e.g. remove old assignments (done) > > - default #rendererClass changed, most components converted (mostly done) > > - several fixes to rendering canvas (mostly done) > > - #updateRoot: to use a canvas like API (done) > > - to have a file library in Seaside (done, but not integrated) > > - to clean up WARequestHandler and friends (open) > > - clean up the code using SLint (started) > > - deprecate unused and old unused code (started) > > > > Philippe? I am sure that I forgot a lot of things! > > - make the root api more canvas like (first version done, we are > trying how it works, first results are positive) > - new very cool deprication mechanism > - full ruby support (backported to 2.6b1) > - even more html elements (backported to 2.6b1) > - WAAnchorTag >> #tooltip has been removed (use #title instead) > - WAListener fixes (backported to 2.6b1) > - other fixes and convenience methods > > > For the timeline: Things just happen as we need them and as we have > > time to work on (for me this is very limited at the moment). > > > > We are using this version in several open-source and commercial projects. > > I saw the Ruby methods in 2.7a and you mention "full Ruby support" above, what's that all about? Thanks, Jason -- Jason Rogers "Where there is no vision, the people perish..." Proverbs 29:18 _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
2006/10/20, Jason Rogers <[hidden email]>:
> On 10/20/06, Philippe Marschall <[hidden email]> wrote: > > 2006/10/20, Lukas Renggli <[hidden email]>: > > > > What's the timeline on 2.7a anyway? I know some people are working on > > > > it, but so far I have no idea who and what direction its taking even. > > > > We'd placed some serious long run bets on Seaside, so any feedback would > > > > be greatly appreciated. > > > > > > Philippe and I started this version at ESUG. One of the main goals was > > > to old renderer deprecated and to clean up the old code, if necessary > > > by explicitly breaking backward compatibility. > > > > > > There are some ugly parts that we would like fixed and that annoy us every day: > > > > > > - clean up the source code, e.g. remove old assignments (done) > > > - default #rendererClass changed, most components converted (mostly done) > > > - several fixes to rendering canvas (mostly done) > > > - #updateRoot: to use a canvas like API (done) > > > - to have a file library in Seaside (done, but not integrated) > > > - to clean up WARequestHandler and friends (open) > > > - clean up the code using SLint (started) > > > - deprecate unused and old unused code (started) > > > > > > Philippe? I am sure that I forgot a lot of things! > > > > - make the root api more canvas like (first version done, we are > > trying how it works, first results are positive) > > - new very cool deprication mechanism > > - full ruby support (backported to 2.6b1) > > - even more html elements (backported to 2.6b1) > > - WAAnchorTag >> #tooltip has been removed (use #title instead) > > - WAListener fixes (backported to 2.6b1) > > - other fixes and convenience methods > > > > > For the timeline: Things just happen as we need them and as we have > > > time to work on (for me this is very limited at the moment). > > > > > > We are using this version in several open-source and commercial projects. > > > > > > I saw the Ruby methods in 2.7a and you mention "full Ruby support" > above, what's that all about? http://en.wikipedia.org/wiki/Ruby_character http://www.w3.org/TR/ruby/ Philippe _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
In reply to this post by Philippe Marschall
2006/10/20, Philippe Marschall <[hidden email]>:
> 2006/10/20, Lukas Renggli <[hidden email]>: > > > What's the timeline on 2.7a anyway? I know some people are working on > > > it, but so far I have no idea who and what direction its taking even. > > > We'd placed some serious long run bets on Seaside, so any feedback would > > > be greatly appreciated. > > > > Philippe and I started this version at ESUG. One of the main goals was > > to old renderer deprecated and to clean up the old code, if necessary > > by explicitly breaking backward compatibility. > > > > There are some ugly parts that we would like fixed and that annoy us every day: > > > > - clean up the source code, e.g. remove old assignments (done) > > - default #rendererClass changed, most components converted (mostly done) > > - several fixes to rendering canvas (mostly done) > > - #updateRoot: to use a canvas like API (done) > > - to have a file library in Seaside (done, but not integrated) > > - to clean up WARequestHandler and friends (open) > > - clean up the code using SLint (started) > > - deprecate unused and old unused code (started) > > > > Philippe? I am sure that I forgot a lot of things! > > - make the root api more canvas like (first version done, we are > trying how it works, first results are positive) > - new very cool deprication mechanism > - full ruby support (backported to 2.6b1) > - even more html elements (backported to 2.6b1) > - WAAnchorTag >> #tooltip has been removed (use #title instead) > - WAListener fixes (backported to 2.6b1) > - other fixes and convenience methods I forgot: - no longer use WeakArrays in Squeak. They don't work. > > For the timeline: Things just happen as we need them and as we have > > time to work on (for me this is very limited at the moment). > > > > We are using this version in several open-source and commercial projects. > > > > Cheers, > > Lukas > > > > -- > > Lukas Renggli > > http://www.lukas-renggli.ch > > _______________________________________________ > > 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 |
In reply to this post by Philippe Marschall
Thanks.
On 10/20/06, Philippe Marschall <[hidden email]> wrote: > 2006/10/20, Jason Rogers <[hidden email]>: > > On 10/20/06, Philippe Marschall <[hidden email]> wrote: > > > 2006/10/20, Lukas Renggli <[hidden email]>: > > > > > What's the timeline on 2.7a anyway? I know some people are working on > > > > > it, but so far I have no idea who and what direction its taking even. > > > > > We'd placed some serious long run bets on Seaside, so any feedback would > > > > > be greatly appreciated. > > > > > > > > Philippe and I started this version at ESUG. One of the main goals was > > > > to old renderer deprecated and to clean up the old code, if necessary > > > > by explicitly breaking backward compatibility. > > > > > > > > There are some ugly parts that we would like fixed and that annoy us every day: > > > > > > > > - clean up the source code, e.g. remove old assignments (done) > > > > - default #rendererClass changed, most components converted (mostly done) > > > > - several fixes to rendering canvas (mostly done) > > > > - #updateRoot: to use a canvas like API (done) > > > > - to have a file library in Seaside (done, but not integrated) > > > > - to clean up WARequestHandler and friends (open) > > > > - clean up the code using SLint (started) > > > > - deprecate unused and old unused code (started) > > > > > > > > Philippe? I am sure that I forgot a lot of things! > > > > > > - make the root api more canvas like (first version done, we are > > > trying how it works, first results are positive) > > > - new very cool deprication mechanism > > > - full ruby support (backported to 2.6b1) > > > - even more html elements (backported to 2.6b1) > > > - WAAnchorTag >> #tooltip has been removed (use #title instead) > > > - WAListener fixes (backported to 2.6b1) > > > - other fixes and convenience methods > > > > > > > For the timeline: Things just happen as we need them and as we have > > > > time to work on (for me this is very limited at the moment). > > > > > > > > We are using this version in several open-source and commercial projects. > > > > > > > > > > I saw the Ruby methods in 2.7a and you mention "full Ruby support" > > above, what's that all about? > > http://en.wikipedia.org/wiki/Ruby_character > http://www.w3.org/TR/ruby/ > > Philippe > _______________________________________________ > Seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > -- Jason Rogers "Where there is no vision, the people perish..." Proverbs 29:18 _______________________________________________ Seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Free forum by Nabble | Edit this page |