MVC

So, if you get model and view, controller is pretty simple from there. The controller is the guy that goes out and talks to the view and the model so that they can share information. Think of the model and the view as siblings that are mad at each other. They don't want to talk to each other. Instead when Mikey wants to communicate with Johnny he tells his mom or dad to "tell johnny I said shut up!". In this example the parent is the controller. They act as a buffer between the other two parties which allows data to remain separate from the views. There is a slide attached from the Stanford iOS course (applies to MVC in general) which has a very good explanation of MVC. You can find it on iTunes U. The lines that form a sort of piece sign work the same way as road makers in his example. White dashed are crossable, etc. Notice the double yellow between view and model. Don't pass in a no passing zone!