Re: IntraApp Communication....
Re: IntraApp Communication....
- Subject: Re: IntraApp Communication....
- From: James DiPalma <email@hidden>
- Date: Sat, 28 Sep 2002 15:57:39 -0400
From: Jonathan Jackel <email@hidden>
There is a heading in the NSApplication docs entitled "Subclassing
NSApplication." It says, in part, "The only reason to subclass
NSApplication is if you need to provide your own special response to
messages that are routinely sent to NSApp. (Even then, NSApp's
delegate is
often given a chance to respond to such messages, so it's more
appropriate
to implement the delegate methods.)"
This documentation is suggesting a good habit for object oriented
programming while pointed out some Cocoa specific functionality.
Classes should be subclassed to modify some behavior that they actually
do. NSApplication delegates many responsibilities that a subclass of
NSApplication may consider doing. Many Cocoa objects (including
NSApplication) don't require subclasses for certain behavior changes.
This documentation is not recommending against subclassing
NSApplication as much as it is recommending that developers understand
how Cocoa is designed to do things before subclassing to change how a
Cocoa Class does something.
-jim
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.