[Seaside] [Newbie] Seaside-Component classes

Philippe Marschall philippe.marschall at gmail.com
Thu May 4 09:07:00 UTC 2006

2006/5/4, Dmitry V. Sabanin <sdmitry at lrn.ru>:
> Hey.
> Here I am again with my stupid questions, unable to find any docs
> online.
> This time my question is about classes in Seaside-Component category.
> I'm trying to understand when to use what, and here's understanding
> that I have to the moment:
> WAAnswerHandler
> ------------------------
> .oO( No ideas here, but for some reason I don't think this class is
> of interest to me at this moment )
> WAComponent
> --------------------
> .oO( Ordinary components. Pretty much no questions here. )
> WADecoration
> ------------------
> .oO( What's this? As I imagine this must be some kind of wrapper
> around ordinary components, to enhance them or wrap some code around
> them? If it's true, how do I add Decorations to my existing component? )
> WADelegation
> ------------------
> .oO( No ideas. Need help :-) )
> WAPresenter
> -----------------
> .oO( This one just drives me crazy. I wanted to think of this as of
> some big master component that acts as a container for all
> application components. Something like "Application Component", but I
> have no idea if it's true. )
> WATask
> -----------
> .oO( If I get this right, this is useful for something like
> Transaction Script (PoEAA)? For example, I can encapsulate some
> business logic in a WATask subclass and make it call components in a
> needed order? Or there's something else meant as a "workflow" in
> WATask class docs? )

I hate make this sound like RTFM but WAComponent, WADecoration, and
WATask (the important ones) actually have a class comment that should
answer your questions. But basically you are right about them.


More information about the Seaside mailing list