[Seaside] Scriptalicious

Lukas Renggli renggli at gmail.com
Mon Jul 31 09:06:40 UTC 2006

> Would it make sense if the decision of which components to update was made
> by some event machinery that tied components to domain objects and detected
> 'dirty' components?

Yes, I once wrote a prototype of something like that for a commercial
project, but it is much trickier than it sounds like, at least for
more sophisticated cases.

The major problem is that the id of the <id, render-code> pair is
dynamic, that is it might change, appear, disappear over the livecycle
of a page. Then the order in which those updates should be evaluated
is not given with a set of <id, render-code> pairs, but the order
might matter for the resulting page.

Maybe I am just thinking too generic? Maybe anyone has an idea how
this problem could be reduced so that we can implement a subset of the
requested functionality?


Lukas Renggli

More information about the Seaside mailing list