[Seaside] Re: Re: Re: Re: Re: Ajax callback question:howtoupdatecomponenttreebefore #children gets called?

itsme213 itsme213 at hotmail.com
Mon Feb 11 17:56:34 UTC 2008

"itsme213" <itsme213 at hotmail.com> wrote in message 
news:fol64u$vqb$1 at ger.gmane.org...
> "Lukas Renggli" <renggli at gmail.com> wrote
>>> Maybe changing the callback method name would help to understand.,
>>> maybe having a keyword (#callback:inComponent:)
>> That doesn't work, because a callback could render to many components.
> I may be way off here, but why does it have to be all in a single 
> callback? Could we do this:
> - Explicitly separate one ModelUpdate vs. many ViewUpdates
> - Allow each ViewUpdate to be callback:inComponent:
> e.g.
> WATagBrush>>
>    onClick: aModelUpdateString then: manyViewUpdatesStrings
> SUUpdater>>
>    callback: aViewUpdateBlock inComponent: aComponent
> html anchor
>  onClick:
>    "do this first (wait for success event?)"
>    (html request callback: [self updateModel])
>  then:
>    "then do this array of updates in parallel"
>     {(html updater
>         "id: anId not required; must be compA id"
>         callback: [self viewUpdateA] inComponent: compA).
>      (html updater
>         "id: anId not required; must be compB id"
>         callback: [self viewUpdateB] inComponent: compB).
>      (html updater
>         "by convention, on current component"
>         callback: [self viewUpdate]). };
>  with: 'do it'.
> It would be nice if something like this could this be done without 
> requiring the user to deal with the underlying Ajax lifecycle events.
> Even better abstracted, if this is a common pattern:
>  onClick: aModelUpdateBlock then: someViewUpdateComponents+Blocks
> Sophie 

More information about the seaside mailing list