Re: IntraApp Communication....
Re: IntraApp Communication....
- Subject: Re: IntraApp Communication....
- From: James DiPalma <email@hidden>
- Date: Sat, 28 Sep 2002 02:32:46 -0400
From: "Steven M.Palm" <email@hidden>
subclassing NSApplication [not recommended, from what I've read]
I wonder why. Where did you read this?
I can see recommending using alternate techniques for solving problems,
like a separate controller, a delegate, notifications
(didFinishLaunching and others), or other solutions. But, I am
unfamiliar with why a subclass would be discouraged if your instance of
NSApplication has to handle a method.
I would recommend either a category that forwards all applescript
messages to another controller, or an NSApplication subclass that
handles applescript messages itself.
Reality is that your code will probably work fine in a few different
locations and what your comfortable with is important, so stick to a
category. I'm just curious why a subclass would be discouraged.
-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.