Navigation |
Cocoa Application ArchitectureCocoa Application Architecture
Posted June 28th, 2007 by Paul
Anyone out there? Why are there never any good examples of best practices for application structure out there for Cocoa. I realize the MVC pattern is a large part of Cocoa and its AppKit framework, but honestly, there’s a lot more to structuring an app than just saying, "use MVC principles". What’s the best way to manage multiple GUI resources—multiple windows, panels, dialog, etc…? Should each "window" be placed in its own nib file? Should each window get its own controller? If so, what’s the easiest way to get the multitude of controllers talking to or knowing about eachother? Globals? Statics/Singletons?
|
User loginApple Developer Connection |