> I think Observer covers it.
>>
>> see http://en.wikipedia.org/wiki/Observer_design_pattern
>
> This gave me the missing piece of the design puzzle.
this is a great example of the power of design patterns. They are way
of encapsulating and propagating "obvious" general knowledge
efficiently.
It is a nice shorthand. You can ask someone, "are you familiar with
the X design pattern?". If not, you can point them to a canned
explanation. If so you may not have to say anything else to help
solve the problem.

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.
Oliver Wong - 22 Sep 2005 22:46 GMT
>> I think Observer covers it.
>>>
[quoted text clipped - 10 lines]
> explanation. If so you may not have to say anything else to help
> solve the problem.
This is very true, particularly when your company hires someone new and
you need to get them up to speed real quick.
Newbie: How does this work?
Oldie: You know the visitor pattern?
Newbie: Yeah.
Oldie: It's like that, except we have multiple types of trees, so we have an
abstract "super visitor", and we use Factories with generics to get the
correct visitors for each tree.
Newbie: Okay, I think I got it.
[If the reader doesn't get it, it's probably because (s)he didn't read the
javadoc package overview for the source code like the newbie did.]
However, in the specific case of my problem being solved, I think what
psychologically cause a "click" in my mind was your use of "Observer" in the
singular, making me realize I wouldn't have to make the menu items subscribe
to each panel individually (i.e. "Observers" plural)
- Oliver