Understanding Model-View-Controller Creating A Class Outline - FIrst App Pt. 3

This is the 3rd tutorial in the series on developing your first Apple iPhone app store app, please visit this page if you have any questions http://maniacdev.com/2009/07/understanding-model-view-controller-and-creating... or post in the comments below. In this video I briefly go over the MVC architecture, and then outline my own method for creating a class outline when developing simple apps.

Please excuse the sound quality in the first minute or so, I recorded that portion of the video outside, and the breeze must have messed with my Macbook.

Category:

Education

Tags:

• iPhone
• 3G
• 3GS
• Apple
• SDK
• App Store
• development
• developing
• beginner
• getting started
• tutorial

[crimsonBen]

what a voice xD

[candygameengine]

@ayumilove That's not entirely accurate.  The model contains the data and business logic. The controller is just "glue code" that acts as a layer between the model and the view. The view does NOT know about the model directly. The controller is in charge of telling the view of changes in the model's data.

[warnpassion]

Thank you very much for the video but as I read the video description, it says it explains the MVC pattern to develop an iPhone application. However, I am more into developing web applications and stand alone applications. So it would have been great if I could get a video which explains the architecture in a more generalized approach. Thank you.

[haazaakilz]

these parts have only told us about it not how to make one

[leemorethomas]

I read the comments before really hearing the video and I'm reading that model and controller, as always, is unclear. The view is easy to understand. I'm become an expert at realizing model and controller are not clearly separated by tasks

[Julzso23]

I've just realised that ur not going to tell or show me anything useful after 3 videos

I'll find another guy who's got a real tutorial

[zipppy2006]

His explanation is actually fairly accurate. He is at least closer than you are: the view interacts with the controller which then interacts with the model. The separations allows for good encapsulation for future changes, as was noted.

You basically restated what was said in the video and then botched it with the bit about the view knowing about the model.

[ayumilove]

Also the view has some controller in it (the logic) to manipulate how the data should be represented.

[ayumilove]

Your definition of MVC (model view controller) is incorrect.

Model is all about information. (the quantity of something)

The view (visual) is all the things that you can see (buttons, textfield, etc)

The controller is the logic (business logic, the fun part)

The view knows about the model, but model does not know about view.

If view does not know about model, how is it suppose to represent the data?

[Grauwsaur]

I was looking for some thoughts on MVC, but this is about simple OOP and identifying objects and doesnt seem to have anything to do with MVC.