Utility window architecture question
Utility window architecture question
- Subject: Utility window architecture question
- From: Brock Brandenberg <email@hidden>
- Date: Fri, 17 May 2002 11:14:33 -0500
I have a number of utility windows in an application that are used as
object inspectors. What I would like to do is to combine them into a
single panel very much like what Omni does in OmniGraffle, but I would
like to avoid bringing all of the associated code into a single window
controller and simply swapping the content view of the window. Separate
windows have the advantage of good code separation, each window having a
custom window controller complete with outlets and actions that are
unique to that window. When using the view swapping method, I feel like
I need all of the outlets and actions in the same window controller,
which leads to too large of a nib file and too much code in a single
window controller to be easily managed (the inspectors each have many
controls).
My question is, does anyone have a suggestion for a good code
architecture for a panel that has its content view swapped out at
runtime? For example, should I be creating a view controller for each
custom view that is responsible solely for that view's contents, then
load and unload each controller and associated nib as appropriate?
Thanks,
Brock Brandenberg
----- industrial design @ bergdesign.com ------
_______________________________________________
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.