[Seaside] Static link to get variables
Florian Minjat
florian.minjat at emn.fr
Wed Feb 15 14:47:41 CET 2006
My aim is to embed a flash menu in my seaside app.
So I need to feed this flash menu with the different links. Thoses
links must be the equivalent of a message call to a seaside component.
I could use the #initialRequest: method to send GET variables to the
seaside app from the flash menu. But when I tried this method, the
context was lost (my app requires an authentification).
I am trying the method suggested by Lukas with :
url := html context actionUrl withParameter: (html callbacks
registerActionCallback: [ mycall ]).
And it seems to work. I need to make more tests to be sure.
Florian
Avi Bryant wrote:
>
> On Feb 12, 2006, at 6:51 AM, Florian Minjat wrote:
>
>> Nobody knows how to do that or is it impossible for the moment with
>> Seaside ? Or perhaps nobody understood what I meant.
>
> I'm not exactly clear on what you meant, no. Where do you want to be
> able to get this URL from?
>
> Avi
>
>> Florian
>>
>> Florian Minjat wrote:
>>> Thanks !
>>> So now i know how to handle request like
>>> http://.../seaside/myApp?foo=bar to start my app.
>>> A little more complex now : I want to do the same, but from an
>>> integrated flash menu. The trick is that I don't want to loose my
>>> session and context. I tried by just adding the '&foo=bar' at the end
>>> of the url (
>>> http://.../seaside/myApp?_k=UeGCjSsi&_s=OTvjybecbYCHpKsn&foo=bar) and
>>> it seemed to work, but I don't know how to get this string for a
>>> particuliar action. Any idea ?
>>> Florian
>>> Avi Bryant wrote:
>>>>
>>>> On Feb 7, 2006, at 12:52 AM, Dmitry Dorofeev wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> You need to subclass WARenderLoopMain
>>>>> and implement (start: aRequest) method
>>>>
>>>> There's a somewhat easier way to do this in recent versions of
>>>> Seaside - after the initial component tree is created by
>>>> #createRoot, every component in the tree will be sent
>>>> #initialRequest: with the request object that started the session.
>>>> This can be especially effective when paired with a WATask subclass
>>>> as the root, so that it can, eg, present a login page as needed
>>>> depending on the request.
>>>>
>>>> Avi
>>>> _______________________________________________
>>>> Seaside mailing list
>>>> Seaside at lists.squeakfoundation.org
>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>>>
>>> _______________________________________________
>>> Seaside mailing list
>>> Seaside at lists.squeakfoundation.org
>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>> _______________________________________________
>> Seaside mailing list
>> Seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>
More information about the Seaside
mailing list