Game framework architecture - view components or MVC? -


Instead of starting my scratch to my game, to create a very light reusable framework for my game I am trying to play a game. I have a component driven architecture - e.g. The institution creates a position component and a health component and AI component etc.

My biggest question is whether to allow more than one view of the model, my model makes visual components or use a real MVC, where the model His thoughts are not known, and they are externally managed.

I have tried both methods, but if a person knows the pros and cons of every approach and that industry is the norm, it would be good to know.

Depending on your audience, the game devs, is very used for the MVC model, though Most know it, due to the number of development casualties (no serious technical reason), it is not easy to cut it clean. With experience, I have started dozens of game structures as MVC, but only a couple was able to keep it till the end. My theory connects MVC with very little gains (usually some dev) for very little complexity and small throw, and in these layers for large / complex games, it is really hard to keep the most game object apart. . And since the game has a release date, they sometimes provide code explanation and re-purpose for display and quick adhoc solutions (if the sequel is needed (if any) will be written again.

However, the above warning, it is better to target high, because if you make it better then it will be better :) And if you fail, then if you fail, you should probably try MVC,But do not worry that it fails, professional game developers have failed many times :)


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -