[Seaside] Home link

[Yar Hwee Boon]

On Wed, 20 Oct 2004 18:39:34 +0800, Yar Hwee Boon <hboon at motionobj.com>  
wrote:

> On Wed, 20 Oct 2004 12:29:27 +0200, Avi Bryant <avi at beta4.com> wrote:
>
>> On Oct 20, 2004, at 12:13 PM, Yar Hwee Boon wrote:
>>
>>> 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.
>>
>> If you're not #answer:-ing, why are you #call:-ing?
>
> Aaargh.. it never occurred to me to swap the components. I guess with  
> the hammer in my hand.. everything looks like its begging for  
> #call-#answer. Thanks for clearing that up.

After studying WASimpleNavigation, and thinking through for a while, I  
realise that I may still need to use #call:. An example would be: one of  
the options is to show a forum. After browsing through the forum for a  
while (#call-ing other components to show different topics, replies, etc),  
and the user clicks another option, say Profile. At this point, if he  
tries to go back to Forum, he should see the "first page" of the forum  
again rather than the last state. So.. in this case, does it look like I  
really need #call without #answer:? I think that WASimpleNavigation  
mirrors how a "tab control" works,whereas what I have is more like a  
simple HTML link.

-- 
Regards
HweeBoon
MotionObj