[Seaside] Seaside Components: Parent / Children
ssastre at seaswork.com.ar
Tue May 16 16:35:55 UTC 2006
Yes but that depends of *how much* it knows about it's parent. For certain
features this could be really helpful. Abuse produce the results you
For a reference:
Presenters are composed by (sub)Presenters and they all know it's
corresponding #parentPresenter in the MPV (Model-View-Presenter) framework.
I've made my own WAPresenter subclass wich is instantiated knowing about it
parentPresenter. I see the same intention in
ShoreComponent class>>parent: aComponent
Until now I have been succeful in a Seaside application that make intesively
use of that subclasses, without coupling.
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Ramon Leon
> Enviado el: Martes, 16 de Mayo de 2006 13:07
> Para: The Squeak Enterprise Aubergines Server - general discussion.
> Asunto: RE: [Seaside] Seaside Components: Parent / Children
> > 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.
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
More information about the Seaside