[Seaside] Re: Re: Re: Re: Ajax delete component only worksif#childrenstillreport all previously deleted components?

itsme213 itsme213 at hotmail.com
Tue Feb 19 19:31:40 UTC 2008

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

>> That was the first thing that got my attention in Michael Lucas-Smith's
>> recent post in the "mootools" thread. (btw, I think your perspective on 
>> his
>> points would be quite insightful).
> I don't exactly see what part you are referring too.

Here it is, relating to render-canvas and callback-registry:

"f) Because there was only ever one page on the server to represent a
single user, there was rarely any memory concerns. There was also no
passes to process actions and callbacks, those were registered in to a
weak dictionary so that if an element was destroyed, so was the callback."

> It uses this component as the owner (which is presumably wrong) of the
> callbacks in partial render passes that follow.

I get it now, thank you. I guess it needs this owner to do things like find 
the decorator-chain (assuming decorators get a shot at wrapping stuff around 
callback executions).

> The question is, what would be useful for other frameworks?

Sebastian makes some good points on jQuery: I've been reading on it and 
jQuery code reads really clean and succinct, it has no conflicts with 
prototype (so incrementally using it is painless), it is nicely OO, cleanly 
separates base library from plugins, very well documented (2+ books!), is on 
the rise, and is getting *lots* of plugins http://plugins.jquery.com/ from 
infrastructure (like AjaxQueue - serialize possible race-conditions) to rich 
UI widgets.

It might be a good 2nd reference point from which to generalize.

Thank you again,


More information about the seaside mailing list