[Seaside] Re: Help with understanding how #call: works

Jeffrey Straszheim jstraszheim at comcast.net
Sun Feb 24 22:25:48 UTC 2008

Malte Zacharias wrote:
> Yep, that's how it's done. You only need to include those components 
> in children which are going to be rendered the next time the component 
> implementing children is rendered. (E.g. if you have html render: 
> aComponent within the rendering code you need to include it) A call 
> actually replaces the component that calls another with the called 
> component (until the called component answers).
In this case, would you have to included the called element in the 
parent's children list?

Jeffrey Straszheim

More information about the seaside mailing list