[Seaside] What's the difference and why??

Brian Brown rbb at techgame.net
Thu Mar 2 17:06:55 UTC 2006

Yeah, I guess that is old.... There is a method on WAComponent called  

It gets rid of all the delegates a component has, so just sending  
#home to your component will do what clearAllDelegates did.


On Mar 2, 2006, at 7:11 AM, Cédrick Béler wrote:

> Hi :)
> Really interesting discussion :)
>>> Do you mind if I ask what "clearAllDelegates" does?  I found  
>>> that  it is part of Seaside, but didn't see anything that
>>> really explains what its for..
>> This is one of the very cool parts of Seaside... the #call:  
>> #answer:  methods. What happens is that you send the #call:  
>> message with a  WAComponent subclass as the argument. The  
>> component that was called  becomes the delegate for the calling  
>> component. For all intents and  purposes, it replaces the calling  
>> component until it issues an  #answer message, then the "control"  
>> is returned to the calling  component. The renderContentOn: method  
>> of the top delegate is the one  that is rendered, all the other  
>> delegates in the chain are  effectively invisible. You can chain  
>> as many of these #call:s as you  want. clearAllDelegates removes  
>> the delegate chain, so the root  component is the one that is  
>> rendered again.
> euh... I don't find #clearAllDelegates in my image !  Is it  
> normal ? is there another way to do now?
> I have seaside 2.6a3-lr22
> Thanks
> Cédrick
> --------------------------------
> L'ENIT vous invite a sa journee portes ouvertes le 17 mars 2006 de  
> 13h30 a 19h30
> Visite des locaux,  animations, cadeaux a gagner.
> Enit , 47 avenue d'Azereix 65000 Tarbes
> Bus N°1, arret ENI
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the Seaside mailing list