Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
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 ?
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.