A fast, easy to use, free, and community supported 2D game engine
I'm a fan of the Model-View-Controller design pattern. In game programming, often it unnecessarily increases complexity, but sometimes it's useful.
I could not find any example of an implementation of a model, so I decided to roll my own, inspired by Flixel, an ActionScript game engine:
I've been doing web development for over five years, but I'm new to game programming. I still have much to learn :) Please let me know what you think.
http://tonyngo.net/2011/09/model-implementation-for-cocos2d/
Looks interesting - for me though, MVC is a very good way of writing easy to understand / maintain code (once you know the MVC pattern) but it probably isn't the most efficient / flexible of systems and when it comes to games, you don't want to be wasting any processing power at all.
I would be interested to see a more complete example.
@phil_me_up thank you for responding. How can I make the example more complete?
@psykano I see :) It wasn't my intention to provide a complete example MVC itself. I wanted to show how to group variables into an object and bind to value changes, all without the complexity of defining custom delegates or using notification observers. I'm not sure if my approach is the right way; that's why I'm asking for opinions. Hopefully experienced developers could shed some light :)
I agree. You should use Observer pattern to handle changes in Model.
In Objective-C KVO is the best way to do it.
KVO is Key-Value Observing method (little googling should help ;-)). In iPhone programming there are 2 options when bringing observing topic on the table; using KVO or NSNotification. For Model changes seems to me that notifications would be better option.. On the other hand, KVO is much lighter.. Not really sure, what do you think?
You must log in to post.
