Too many controllers, models, and views
Too many controllers, models, and views
- Subject: Too many controllers, models, and views
- From: David Wood <email@hidden>
- Date: Sat, 21 Jun 2003 21:54:28 -0400
Hello again folks... I have hit the next peculiar point in my project:
either I implement drag & drop to connect the data types in the two
NSOutlines I've got in the main document window, or I create the
information windows, NIBs, and hook-ups for the three data types I have
so far (and there will be more).
I decided to tackle the latter, and already regret it.
As it stands, I have two different controllers: a SubplotController
which controls one of the NSOutlines and manages one of the data trees
(which so far contains only subplots and roles), and a
CharacterController which controls another NSOutline and manages
another data tree (which so far contains only characters). Ideally
things would be dragged between the two to form links between the two
trees.
Except now I'm trying to introduce individual windows to set the
specifics of the characters, subplots, and roles. It's starting to look
like every character, subplot, and role (and anything that follows) is
itself going to turn into a window controller (wrong) or at least a
split data/view object (even wronger).
Can anyone suggest how I should be doing this instead?
--David
http://skipjack.bluecrab.org/~dwood
"I'm *grateful* for my apathy. SOMETHING has to keep my burning,
festering hatred of life itself in check..."
_______________________________________________
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.