[Seaside] Re: Ajax callback question: how to update component treebefore #children gets called?

itsme213 itsme213 at hotmail.com
Fri Feb 8 08:26:24 UTC 2008


"Lukas Renggli" <renggli at gmail.com> wrote in message

> Callbacks are always executed in the context of the defining
> component. So when callbacks are processed the whole component tree is
> traversed (using the information from #children) and the callbacks are
> triggered in the right order in the context of their owning component.

Given a component tree with [zoom] callback operation on C3:
C1
  C2
    C3 [zoom]
can the zoom callback on C3
    C3>>zoom
safely add a child component to C1? From your explanation it appears that 
#children has already been called on C1 & C2, before C3#zoom matches the 
callback search and executes ... and changes C1>>children ... a recipe for 
trouble?

In my app an N-level deep sub-component, on 'Zoom', adds a new tab to the 
top-level tab panel. After this then things appear to break with 
Component-Not-Found.

Please tell me there is a way to do this without losing Ajax :-)

Thanks - Sophie





More information about the seaside mailing list