Introduction

##Motivation

After working for nearly 2 year with JavaScript and more specifically on JavaScript game development, I've gotten very fond of it. With a little study of this language you can find that a once thought of a toy language for DOM events and sticking AJAX petitions, is a very powerful tool that's present on every single browser in the world. Over the last years game developers have realized the power of these language and build a set of powerful tools for building from a small quiz with a question and a few buttons to a whole 3D MMO game.

Unfortunately not everything is joy. Due to the different browsers (and it's versions), the OS and the multiple devices, programming can turn to be a nightmare of hot-fixes to make sure your code will work as you intended everywhere.

Thus is my wish to collect all the experiences I've had making mini-games for my company and blend them into a wrapper that allows to learn how a section or an entire JS game engine works, and at the same time, to be able to make a game with it.

##Objectives

The objective behind this final project is to offer an wrapper API that collects all the basic needs for an HTML5 game to be implemented. Leave the API opened so it can be extended or make use of different implementation so students can try the wide variety of libraries available on the JS environment.

Make the Wrapper from a requirements specification, which will be extracted from an analysis of the basics needs a videogame has. Make a complete GDD of the game.

Use the Wrapper to make the game Crazy volley , this way it can be tested for errors and flaws on it's design. The main is to get the Minimum viable product or MVP, that will result in the possibility of making simple games as the requirements to make full complex game are out of the scope of this project.

Maintain all the project open source during and after its development.

##Project structure

On the state of art chapter, the JS environment will be analyzed from a game developing perspective. After a brief introduction to the ecosystem, a SWOT analysis will explain the benefits and disadvantages of making web games.

The following chapter will discuss the most used features on game frameworks, the wrapper general architecture and the specification of the API .

In the implementation chapter, talk about the development environment, extension. Extension mechanisms of the wrapper and deployment into production through a static objects pipeline is also discussed as is very important for web technologies.