1 Reply Latest reply: Jun 30, 2012 10:48 AM by Llessur999
mark133 Level 1 (65 points)

So it looks to me like Cocoa is set up very well to make one MVC application per project, with one window, one controller, and one model per group?


And then multiple projects or other resources are linked together or else bound together through messaging, a controller, or else through a script, if key-encoded?


Or should the multiple Applications (each composed of one MVC group) be stored within the same project?

  • Llessur999 Level 4 (1,190 points)

    Depends on what you are trying to accomplish and how you are planning to deploy.


    Cocoa applications are not restricted to a single controller or model. For example, a storyboard can contain multiple navigation controllers, each with multiple view controllers. Each controller is essentially a separate MVC implementation. They can share the same model or each have their own model.