I was looking recently for info in Flash Game’s patterns, and google didn’t took me to your blog, but I knew I’ll find useful information here.

I would like to know what is your pattern of choice (for example for the Gravity Pods 2). I was wondering whether an mvc pattern is suitable for a game (for example your Gravity Pods 2, or any other game like in fact…).

As i’ve seen in the pure MVC site this game has been done with pureMvc: http://www.generationgreen.co.uk/Games/eco-rangers/

I am just trying to figure out what base structure/pattern to use (not any framework/toolkit itself – i agree with ian, and I also like to control my own creation without relaying much in 3th party frameworks-) . I would love to have information about how you structure your games or what do you recommend as you have a remarkable experience in this field.

Thank you very much,

Martín.

I think things depends on the nature of the project really. For most flash websites or simple games you don’t need a big framework, this will just be over-engineered counter productive.
For software development with a big team and long terms projects you probably needs a set of rules everyone comply to, else it will be total chaos, but also to be reasonable with it, else it will be a dictatorship and also counter-productive!

We just want exactly what we need, when we need it! It is all about keeping balance between too few and too much.

In my mind the more code is written the more difficult it will be to conceptualize it as a whole and manage it. After all programming and OOP is just the way we convert our ideas into the machine. So it is important to keep things simple. Which means we don’t lose control. And it makes things much simpler for to have a set of small components we can rely on. So Thumbs up to the toolkit!

“Using something like an off the shelf MVC framework is probably ok (if that is what you want), but you will always fight against things if they aren’t custom for a project.”

That’s pretty much exactly what I was saying. Or trying to say. Of course, having your own framework and tweaking it per project gets around a lot of that. Of course there are pros and cons with that method too.

Anyway, I do what I can to avoid using words like “right” and “wrong” in anything development related. Everything has its pros and cons and it’s a matter of weighing those to come up with a decent solution for your project. The only “wrong” thing is not to think about it at all.