Is this common at all, or even useful? Let’s say I build a 2-Dimensional RPG using ORM architecture in an MVC pattern, for example. Are there benefits?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is this common at all, or even useful? Let’s say I build a 2-Dimensional RPG using ORM architecture in an MVC pattern, for example. Are there benefits?
An ORM is a typical business software pattern, not something used in game. I guess you could use an ORM for loading the levels from a database and use it to save the current status when the game is quit. But that wouldn’t be the main focus of the application. A typical business application’s focus is to manage data, so the ORM takes a central role. In the game, the focus should be on the user interface.
Using an MVC approach to building user interfaces is almost always good. It keeps the user interface code structured.