[Seaside] children & egg problem

[radoslav hodnicak]

On Wed, 8 Sep 2004, Kamil Kukura wrote:

> radoslav hodnicak wrote:
> > I did that and noticed a weird thing. Imagine a root component with two
> > columns, navigation left and "main" right (just like the old squeakmap
> > browser example). Navigation causes #call:s in the main component. The
> > main is #render:ed hence it should be in children(*).
>
> I may be wrong, but this scenario confuses me with flow control. In what
> time/stage do your #call:s are getting cleared (being #answer-ed)?

the navigation column is build like

self main activeComponent actions do: [:action|
 html anchorWithAction: [self main activeComponent perform: action] text:
(self textFor: action); break]

action usually looks like "self call: SomeViewer new" or so. And while the
SomeViewer is displayed, action may be e.g. "self call: SomeEditor new"
etc. As you can see, the main component gets "nested", while navigation
always comes from the active component. on answer it just pops one level
up

rado