Am Do,21.08.2008 um 06:10 schrieb Graham Cox:
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 usual approach. What's the problem with subclassing?
An unsubclassed NSWindowController isn't really all that useful. Why
is subclassing so often referred to as "inelegant"?
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. delegates.
But, of course, sometimes a subclass is simply the right thing.
That's what OOP is for.
Not all OOP languages use classes. I. e. look at SELF, a prototype-
based language.
But Objective-C is a class-based language, yup.
Cheers,
Amin
Graham
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/negm-awad%40cocoading.de
This email sent to [EMAIL PROTECTED]
Amin Negm-Awad
[EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
