Re: Strategy to split up large class files?
Re: Strategy to split up large class files?
- Subject: Re: Strategy to split up large class files?
- From: Allan Odgaard <email@hidden>
- Date: Wed, 30 Jun 2004 22:17:55 +0200
On 30. Jun 2004, at 14:29, Arthur Clemens wrote:
The problem I have is that each part has some relation to the
interface. If I separate the registration part to a category, the
IBAction methods are not accessible in Interface Builder (or should I
leave the declarations in the AppController.h? - this seems to get
messy).
I didn't catch the start of this thread, so I do not know what you are
doing, but you can either use the First Responder-proxy as target for
your actions (the action message is then sent to the first object in
the responder chain which responds to it), you can instantiate other
objects in the MainMenu.nib (perhaps singletons, similar to how IB
currently has a Shared User Defaults, Font Manager etc. to which you
can bind) and you can split your Nib into several Nibs -- e.g. a
preferences window could be pretty self contained.
_______________________________________________
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.