Newbie multiple controller design question
Newbie multiple controller design question
- Subject: Newbie multiple controller design question
- From: Steve Gran <email@hidden>
- Date: Thu, 15 Dec 2005 10:17:33 -0800
I have a newbie design and organization question. And as anyone who
has read my posts in the past knows, when I say newbie, I really mean
newbie (as in I don't have a history as a programmer).
:)
But thanks to many posts (and patience of the people I've traded
posts with) my knowledge is continuing to grow and I am now working
on (well for me at least) a larger program. It's not a document
based app and it has quite a bit of ui stuff on a single window. It
has three tableviews, each with it's own nsarraycontroller using
bindings. I am currently using a single app controller which is the
content owner of the three arrays. Not sure if this matters but some
more info: each array contains objects from separate classes (so,
array1 contains objects from my class1, array2 contains class2
objects, etc.)
My question is, is that an acceptable way to handle a single window
(non document) app with lots of tableviews/arrays/other ui stuff? Or
should I be dividing up (things like the content arrays) into
separate controllers and then have a master controller which
interacts with those controllers as well as the other ui stuff
(buttons, textviews, etc.).
I'm a little scared of doing that because I'm not 100% sure how I
"hook up" all the controllers to work together. For example the
program displays certain data (in a textview) from one or another of
two of the arrays depending on certain conditions (checkboxes being
selected, etc.). Although from one of mmalc's examples (Combanants)
I kinda get a general idea.
_______________________________________________
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