Model-View-Controller (MVC) in Games

[Roquen]

Where's the beef?  Validity isn't the problem.  The core issue is meeting one's design spec at minimal engineering costs.  Sure you can implement the walk of a red-black tree as the visitor pattern but it's pure wankery.

[Don Kiddick]

"Controller : the behavior of a model, modifies the state of an object"

In my opion, this is one of  themost common falicies of  MVC. The role of the controller is actaly quiet specific, although very badly name. It'S roles is to intepret user gestures from the View and interpret them into something the model can undertsand.

The model should contains not only the state but the behaviour of the model. Otherwise you get an anemic domain model hhttp://martinfowler.com/bliki/AnemicDomainModel.html.

Which ican be ok, but misses out the OO goodness. Also pushing more functonility into your model makes it easer to write unit tests - the model is the most easily tested.

</Pontification>

[ReBirth]

I don't know how to properly implement the true/real MVC in game but I tried. It's close enough and works fine.

Games published by our own members! Check 'em out!

[Don Kiddick]

to follow up, the role of the Controller is to interpret events from the ui and interpret them into the language model.

It isn't a place to put 'control logic' which is pretty meaningless.

Anyway, I'm glad your solution works.