Re: Composite. Again!
From: Ilja Preuss (ilja.preuss_at_web.de)
Date: 04/08/04
- Next message: Ilja Preuss: "Re: Composite. Again!"
- Previous message: christopher diggins: "Why ABC's make bad Interfaces"
- In reply to: Daniel T.: "Re: Composite. Again!"
- Next in thread: Daniel T.: "Re: Composite. Again!"
- Reply: Daniel T.: "Re: Composite. Again!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 8 Apr 2004 21:04:18 +0200
> Now the programmer can choose. He can put several views into a window,
> or he can create a CompositeView class that manages multiple views as a
> unit, and only put _that_ into the window.
Yes. Of course now the question becomes: Which of the two solutions *should*
a programmer use (and when).
BTW, if I were the programmer of both the Window/View classes *and* their
clients, I would wait implementing the "multiple views per window" approach
until I decided that I want to actually use it.
Cheers, Ilja
- Next message: Ilja Preuss: "Re: Composite. Again!"
- Previous message: christopher diggins: "Why ABC's make bad Interfaces"
- In reply to: Daniel T.: "Re: Composite. Again!"
- Next in thread: Daniel T.: "Re: Composite. Again!"
- Reply: Daniel T.: "Re: Composite. Again!"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
