[Seaside] Re: seaside Digest, Vol 83, Issue 25

Sebastian Van Lacke svanlacke at caesarsystems.com
Tue Nov 24 15:20:15 UTC 2009


Thanks Luckas, that works too.

aRoot javascript document: self example2Script

Sebastian Van Lacke

> Message: 6
> Date: Mon, 23 Nov 2009 22:12:41 +0100
> From: Lukas Renggli <renggli at gmail.com>
> Subject: Re: [Seaside] Adding javascript without encoding
> To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
> Message-ID:
> <67628d690911231312n3b573b20oc7a672fe72f525d0 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I assume that you are in Seaside 2.8, because this problem seems to be
> fixed in Seaside 3.0?
>
>> Component >>updateRoot: aRoot
>>
>> super updateRoot: aRoot.
>> aRoot javascript add: self example2Script.
>
> You probably should use #document: instead of #add:
>
>  aRoot javascript document: self example2Script
>
> Lukas
>
> -- 
> Lukas Renggli
> http://www.lukas-renggli.ch
>
>
> ------------------------------
>
> Message: 7
> Date: Mon, 23 Nov 2009 13:47:54 -0800
> From: Julian Fitzell <jfitzell at gmail.com>
> Subject: Re: [Seaside] Using URL Parameters
> To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
> Message-ID:
> <4a5dbd430911231347x1cda9659j364f3e0d350dcbfb at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Sun, Nov 22, 2009 at 1:54 AM, Lukas Renggli <renggli at gmail.com> wrote:
>>> to extract parameters from URL, you have to make your own
>>> WAApplication subclass, where override 'handleRequest: aRequest'. 
>>> Something
>>> like this:
>>>
>>> handleRequest: aRequest
>>> | blogdate |
>>> blogdate := aRequest at: 'blogdate'.
>>> ^ super handleRequest: aRequest
>>
>> Subclassing WAApplication is discouraged and normally not necessary
>> (Seaside 2.6 and earlier required that). Simply override
>> #initialRequest: in your root component.
>>
>> Have a look at WABrowser and the other components that override
>> #initialRequest: and #updateRoot: to see some examples. This works
>> exactly the same in Seaside 2.8 and 3.0.
>
> His example included a session key in the URL. If that session key is
> valid, #initialRequest: would not be called since it is not the first
> request to the session. In Seaside 2.8 you can use "self session
> currentRequest"; in Seaside 3.0 "self requestContext request".
>
> Julian
>
>
> ------------------------------
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
> End of seaside Digest, Vol 83, Issue 25
> ***************************************
> 



More information about the seaside mailing list