[Seaside] Seaside Components: Parent / Children
rleon at insario.com
Tue May 16 16:44:03 UTC 2006
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf
> Of Sebastián Sastre
> Sent: Tuesday, May 16, 2006 9:36 AM
> To: 'The Squeak Enterprise Aubergines Server - general discussion.'
> Subject: RE: [Seaside] Seaside Components: Parent / Children
> 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 mention.
> 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.
Sure, it's not a problem knowing about or accessing the parent, if all parents can be treated the same, and it's often quite useful. It's when a child has knowledge of a specific parent that the problems begin.
More information about the Seaside