-
Notifications
You must be signed in to change notification settings - Fork 0
Justify
Lots of game engines are available to make games in HTML5 or have ways to export to JavaScript. These programs are powerful, complete and extensible pieces of software tested and ready for developing a professional game. So if there are so many engines. Why this final project?
##Learning Purposes
It's true there are very good game frameworks but they are oriented to making games, not lo let people what it is required to make those same games. Some of the have private proprietary code bases, or are really bad documented inside or can simply be overwhelming for someone who has just entered this world and wants to know how a simple game is made.
##Modularity
In object-oriented programming there is a say: You wanted a banana but what you got was a gorilla holding the banana and the entire jungle. Meaning that even though you can only want a small functionality, you have to carry around the whole environment. It can also be applied to this situation, to test a physics system you must know the whole objects system, the update loop,... Instead with a wrapper that has a defined interface you know what you have to implement to get it working.
##Proposal
A set of interfaces that implemented and bundled together can get a simple game running. the implementations must be easy to adapt and change. Also the wrapper must be extensible so new custom functionality can be added without modifying the core.
#Index