designing beyond MV and (one) C
designing beyond MV and (one) C
- Subject: designing beyond MV and (one) C
- From: Daniel Child <email@hidden>
- Date: Sat, 12 Jan 2008 17:39:37 -0500
Hi All,
Until now I've been doing very simple apps with a number of model
classes, a view, and a single controller.
I am now going to try a more complicated interface, but don't quite
understand how to apply the MVC paradigm in this case. (Just to be
clear, this is NOT a document app, just a plain Cocoa app.)
I'm building a utility to take various types of data and parse them
according to my settings. I'm looking to have an introductory window
that asks what type of file the user wants to parse. Then based on
the response, I open the appropriate window to gather data about the
file to be handled. Separate interfaces will be used for the
different types of parsing operations.
In the MVC paradigm, do you typically use a different controller for
each major interface? Should I have three controllers, one to handle
each type of parser? Three window controllers, to handle each major
settings interface?
What about nib files? I've read that putting everything in separate
nibs is more efficient in terms of loading time, but for quick and
dirty apps, it would be nice to be able to use the "one nib has all"
approach as well. Besides, this is not a time-critical app.
Currently, I have one controller, four windows (intro, and three for
the different setting types), all in one nib file. I can open and
close the separate windows fine. But is that bad design?
Thanks.
Daniel
_______________________________________________
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