[Seaside] Seaside Components: Parent / Children

[Ramon Leon]

> Avi Bryant wrote:
> >
> > So why not have the different WATasks configure the 
> WAComponent they 
> > are creating slightly differently?
> > I'm generally quite suspicious of code that knows too much implicit 
> > info about the context in which it is used.
> >
> 
> In one direction or another the components will be coupled 
> (parent configuring child or child reacting to parent) so why 
> is one direction better than the other?
> 
> It seems to me both are valid?
> 
> - Zulq

When the parent does the configuring of the child, the component is
loosely coupled and reusable, it can have many parents, the reverse is
not true.  A child component that knows about it's parent, is usually
limited to only work when used with that parent, tightly coupled, and
not reusable.