[Seaside] Re: Menu component - communicating with root component
ramon.leon at allresnet.com
Mon Apr 21 15:23:40 UTC 2008
> Peeking at grandchildren is IMHO even worse than accessing a parent.
> It's the same principle (traversing the component
> hierarchy), just more laborious.
Peeking for no purpose other than to do an #includes to scope an
announcement to a particular parent is not IMHO that bad at all. It creates
no specific coupling that's break the component were it moved or the
hierarchy changed and the point in using Announcement/Events in the first
place is to avoid tight coupling. If you can avoid it, certainly, do, but
Kieths proposed problem begged for such scoping of a generic event to a
particular parent so two instance of the same component be used on the page
together without interfering with each other.
More information about the seaside