Gamma is a modular library that is split into many files. Whilst you can use a combined and minified version of the library, as shown in the getting started section, it’s a lot easier to develop and debug your game if you can view the full source code. This allows you to see the code where errors originate from and set breakpoints in the Gamma library.
To make the process even easier, you can also use the development server found in the support directory of the repository. However, for just executing your game, you can just create a html file as explained below. Either method still requires a copy of the source code, which can be gotten by running git clone git://github.com/Royce/GammaJS.git.
To make your own html boilerplate files :
Follow the getting started section.
Get the libs.js from the support/lib/compiled directory.
Inside game.html, replace the head element with the following:
Change baseUrl to point to the folder that contains the gma folder. So if you have the following folder structure, then baseUrl would be "GammaJS".
game.html game.js require.js libs.js GammaJS/ gma/ support/ docs/ examples/ media/
In turn, this means you need the development server to be able to run the tests. However, once you have it setup, running the tests is literally as simple as clicking a link.
Different parts of the development server require some environment variables to be set that point to where you have different parts of the code. If you keep the same structure as found in the repository, then the following environment variables should work.
GMA = /path/to/GammaJS GMA_SRC = $GMA/gma GMA_SUPPORT = $GMA/support GMA_MEDIA = $GMA/media
For an explanation of how it all works and general notes about the code, read the readme files that exist inside the support folder.