Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Multi-MVC projects

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?

iMac

Posted on Jun 27, 2012 9:46 PM

Reply
Question marked as Best reply

Posted on Jun 30, 2012 10:48 AM

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.

1 reply
Question marked as Best reply

Jun 30, 2012 10:48 AM in response to mark133

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.

Multi-MVC projects

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.