Nice tutorial. This example demonstrates straight ...

2011-06-27T01:53:59.013-07:00

Nice tutorial. This example demonstrates straight forward way to present a game content. However, it is interesting how the game design would look like if there were a separate menu mvc (with xib interface). Matt, do you have any ideas how should the clean design look like, made of three MVSs: main app delegate, menu mvc and game content controller (mvc)? It is obvious that all games need some general methods for loading/saving game data, restarting/resuming and etc. Everything is clear when the game is a straight forward - main app delegate with window and game mvc. The main app delegate handles such events as applicationDidBecomeActive: and applicationWillResignActive: and uses all game prep methods there. Now, the situation is a little bit different if we have a menu mvc (for example built with interface builder). Both, main app delegate and menu class needs to point to the same game controller object. But the question for me is, how and where should the game be restarted, resetting the game content object and both pointers (app main delegate and menu)?

Core animation is great, but i still prefer OpenGl...

2010-10-01T16:21:17.000-07:00

Core animation is great, but i still prefer OpenGl cause it is cross plateform.

To my opinion, making the model into a singleton is not a mvc idiom anymore. You can call it, anywhere and that's not what we want. Moreover it's seems that the implementation rely too much on the gameModel interface. I always stay in touch with my model via a custom observer pattern (and not by NSNotification even if there are made for it). But i think i'm a little too psycho-rigid.

As Alex said, i'm wondering the best way to implement a mvc philosophy in a game

Comments on Cocoa with Love: An Asteroids-style game in CoreAnimation, Part One...

Nice tutorial. This example demonstrates straight ...

Core animation is great, but i still prefer OpenGl...