[Seaside] Re: Help with understanding how #call: works
Malte Zacharias
malte.zacharias at nordakademie.de
Sun Feb 24 21:53:47 UTC 2008
Hello David,
> I have a follow up question.
> I am assuming if I do a
>
> self call: componentX
>
> that I do not have to add componentX to the calling component's list of
> children. Is this true?
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).
Hth,
Malte Zacharias
More information about the seaside
mailing list