[Seaside] Tasks and reusing components

Julian Fitzell jfitzell at gmail.com
Mon Mar 1 00:31:22 UTC 2010

On Sun, Feb 28, 2010 at 7:35 PM, radoslav hodnicak <rh at 4096.sk> wrote:
> On Sun, 28 Feb 2010, Julian Fitzell wrote:
>> http://code.google.com/p/seaside/issues/detail?id=553
> It's tricky, isn't it. In previous versions of seaside, the transaction
> filter was implemented as a decoration on components, but it doesn't seem
> like decorations now get a chance to poke at callbacks anymore?

Correct. They don't. This made several things a *lot* simpler but it
is kind of a shame.

> Speaking of which, is there a seaside3 architecture big picture document
> available somewhere? I can't quite wrap my head around all these
> configurable/pluggable/inheritable/whatever bits that come together to make
> everything work. The number of seaside classes has roughly doubled bettween
> 2.5 and 3.0 (not counting tests and javascript libraries), which isn't a bad
> thing per se, but it does make it harder to study the code.

I was working on one and I do still intend to finish it off as we come
to a final release of 3.0. Just because I intend to, doesn't mean I'll
succeed though... I have been saying that for a while. Still, I'm
almost inspired. I 100% agree it is needed.

That said, I firmly believe the code should actually be *easier* to
understand now, particularly because you can now understand almost
everything in terms of the Core package. If you ask questions, that
will force me to reply and thus generate content for the "big picture
document". :)


More information about the seaside mailing list