views:

575

answers:

1

Hi there, I have made two games for the iPhone already, the first one was a mess, and the second one is less messy but still, not perfect.

I would love to hear if someone had some links that pointed to good class organization advice when creating games using MVC ?

+2  A: 

You controller is the glue that holds everything together, it is the least reusable out of the MVC trio. Your views and models are what you should concentrate on making reusable. The controller handles all of the game-specific manipulation. The models are what the controller manipulates.

Don't design for the future either, just get a good basic design in place, and try to code while sticking to that design. Don't refrain from refactoring.

See my question on Implementing MVC the right way.

Sneakyness
Through the controller your views and model become reusable, but if one can make a controller reusable why not do it?
Daniel
You can't have all three, you'd end up with hundreds of lines of generic code that don't do anything specific well. You're better off sticking to keeping the views and models reusable, with a utilities class that has all the functions you find yourself using in every game.
Sneakyness