Benefits of subclassing NSWindowController?
Benefits of subclassing NSWindowController?
- Subject: Benefits of subclassing NSWindowController?
- From: James McConnell <email@hidden>
- Date: Mon, 21 Mar 2005 20:37:05 -0600
Greetings, all. This post comes in light of the recent thread on rewriting
a large project. I am actually getting ready to start on a large project
myself, not rewrite one. It's not document-based, though. It mainly
involves three main sections, each one managing a separate part of the
overall application.
What would be the benefit of subclassing NSWindowController as my
"application controller", or should I just subclass NSObject per usual? I
plan on having three main windows, each doing something separate from the
others, so I plan on having each in their own nib file and controllers. But
I am going to need one main controller to manage some overall aspects of my
application design.
Should I use NSWindowController as my overall controller? What would be the
benefits of doing so? Or should I just use NSObject?
I can go into more detail about the design and function of my app if it will
help. This is mainly a design question in nature, as opposed to something
specific. Thanks in advance, all.
James
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden