[Seaside] Home link
Giovanni Giorgi
jj at objectsroot.com
Wed Oct 20 12:32:53 CEST 2004
Try to use goto: it works well.
This code was posted by avi a lon time ago
goto: aController
"
I should also point out the methods #willCall and #willAnswer on
WAComponent (actually its superclass, WAController). By default these
return true. If you know, however, that your component either never
sends
#call: or never sends #answer:, you can override them to return
false and
Seaside will make the appropiate optimizations. So that, for example,
making a #call: to a component that has #willAnswer returning false is
effectively a #goto:.
By avi at beta4.com
"
delegate contents: aController
Yar Hwee Boon ha scritto in data 20/10/2004 12.13:
> On Wed, 20 Oct 2004 11:58:30 +0200, Avi Bryant <avi at beta4.com> wrote:
>
>> On Oct 20, 2004, at 10:24 AM, Yar Hwee Boon wrote:
>>
>>> Are you saying it is OK to send #call: to a component multiple times?
>>
>>
>> Yes, it's ok, in that it will work. You may want to send it #home
>> before sending it #call: the second time, depending I guess on what
>> you want to have happen when the second #call: answers - do you want
>> to be back at the original component, or at what it had previously
>> called? The calls will work like a stack - you can push a new one
>> on, but when that's over you'll be back into the previous one unless
>> you clear it first.
>
>
> It's a navigation bar where there's links to several different
> "screens". I wouldn't be #answer:-ing from those calls. I take it
> that, I should send #home before a second (or third, etc) #call then.
>
>
>
--
.............................................................
Giovanni Giorgi ObjectWay SpA - Milano
http://www.objectway.it via Boltraffio, 7 - 20156 Milano
.............................................................
More information about the Seaside
mailing list