how to pass data from table view to second view controller?

Model-View-Controller Pattern: Encapsulating logic and graphics in the same class?

• Alright, so I realize that the MVC is the "responsible" design pattern, but it seams to make things more complicated and I just cant wrap my head around it. I'm currently programming a maze game for the Iphone, now according to the MVC I store the maze grid data in the model class, iterate over said data in the view-controller which then draws said data onto the view (please correct me if I'm wrong). When I think of an object orientated programming architecture I always think of how the objects work in real life. In my observation real life object contain their graphical information too. Would it be a crime against all programming gods if I just included my maze grid logic in the view class, so that I can draw data while it being generated? It would also make everything much more compact and give me a better overview? Thanks!

• Answer:

  Would it be a crime? No. Would it land you in MVC jail? Maybe. If the logic you want in the view layer is how to *present* the data, you're in the clear. That's totally what the view is for: show the user stuff. It's perfectly acceptable to have logic in your views, as long as the primary purpose of the logic is presentation of data from a model. Compactness isn't the point of MVC—it's being able nimbly add new features and react to problems quickly. Occasionally you "denormalize" or crunch things together to squeeze more speed out of your application, but that's a delicate balance you'll need to manage on your own. ;)