On Aug 21, 2008, at 10:12 AM, Negm-Awad Amin wrote:
Probably because the GoF prefers combination over (?) subclassing.
Subclassing always discloses parts of the implementation of a class.
(white-boxing) So generally it is a good idea, to look for
alternatives for subclassing, esp.
Am Do,21.08.2008 um 19:24 schrieb j o a r:
On Aug 21, 2008, at 10:12 AM, Negm-Awad Amin wrote:
Probably because the GoF prefers combination over (?) subclassing.
Subclassing always discloses parts of the implementation of a
class. (white-boxing) So generally it is a good idea, to look
On Thu, Aug 21, 2008 at 12:59 PM, Gerd Knops [EMAIL PROTECTED] wrote:
No problem with subclassing. It was just the presence of the
'-initWithWindowNibName:owner:' method that tripped me off a little, as it
seems near useless unless there is some undocumented magic behind it.
I don't see why
I have a NSWindowController subclass managing a window and some
functionality in that window. Now at some point I need to display a
sheet, which is a window in a different nib.
I'd like to use another NSWindowController to load that nib file,
mainly so it will take care of (eg release) all
On Aug 20, 2008, at 1:39 PM, Gerd Knops wrote:
I have a NSWindowController subclass managing a window and some
functionality in that window. Now at some point I need to display a
sheet, which is a window in a different nib.
I'd like to use another NSWindowController to load that nib file,
On Aug 20, 2008, at 1:57 PM, Ken Thomases wrote:
On Aug 20, 2008, at 1:39 PM, Gerd Knops wrote:
I have a NSWindowController subclass managing a window and some
functionality in that window. Now at some point I need to display a
sheet, which is a window in a different nib.
I'd like to
On 21 Aug 2008, at 5:13 am, Gerd Knops wrote:
That'd work, but I'd have to subclass NSWindowController for that so
I can add that property. Seemed to me that the above would not be an
uncommon pattern and there ought to be a more elegant way that I
might have missed.
Yep, that's the
