beyond MV and (one) C
beyond MV and (one) C
- Subject: beyond MV and (one) C
- From: Daniel Child <email@hidden>
- Date: Sun, 13 Jan 2008 11:59:05 -0500
Chapter 5 section 4 is about the target action paradigm. If you mean
Chapter 4 (Cocoa Design Patterns) I had read that (and just reread
it), but I don't see obvious answers to my question. Maybe a clue is
buried in the discussion of mediating and coordinating controllers.
"In a well-designed Cocoa MVC application, coordinating controller
objects often "own" mediating controllers, which are archived in nib
files."
While that gives me a vague sense that I should explore the canned
controller classes (and bindings), it says nothing about how many
controllers to use for the various model parts. If I understand what
they're saying (and that's a big if), my case boils down to this:
model-controller to choose file type (NSWindowController?) => window 0
model for parsing file type 1 => regular (homemade) controller =>
window 1
model for parsing file type 2 => regular (homemade) controller =>
window 2
model for parsing file type 3 => regular (homemade) controller =>
window 3
I've tried to read all I can about NSWindowController, I don't quite
understand where they fit in, especially if used outside of the
document architecture (which I'm not using yet).
在 Jan 12, 2008，8:40 PM，email@hidden 写道：
In the MVC paradigm, do you typically use a different controller for
each major interface?
This is discussed in <http://developer.apple.com/documentation/
Cocoa/Conceptual/CocoaFundamentals/CocoaDesignPatterns/
chapter_5_section_4.html
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden