What is the correct way of implementing true MVC in Objective-C (Cocoa/iPhone) when the view is NOT created with Interface Builder?
|
|
If I understand the question correctly, you'll still have your model and controller classes. Your view, which normally would come from Interface Builder, is now being constructed in the controller. I like to call the pattern M/VC, where the view and controller are the same, but the model is still separated. |
|||
|
|
|
The MVC framework you're most likely using in the programming language Objective-C is either Cocoa or Cocoa Touch. In Cocoa Touch, for instance, you'll write subclasses of UIView and subclasses of UIViewController. Those classes have concerns and functions that are specific to their functionality either as a view or as a controller. There's more flexibility (and therefore less formal structure) around the "M" part of the MVC framework. Could be you'll use Core Data or some wrapper classes around SQLite or some entirely custom-built data manager object. |
|||
|
|
