pretty much what pygames special_flags argument does: it affects how the two surfaces are composited. compare: * http://www.pygame.org/docs/ref/surface.html#Surface.fill * http://dev.w3.org/html5/2dcontext/#dom-context-2d-globalcompositeoperation
all bash scripts in /bin and renamed, also copied lots of better shell patterns from ringojs scripts (e.g. now they can actually be symlinked into /usr/bin/ and still work :| ) renamed all scripts and output files to better match common minification scripts `app.min.js` and `gamejs.min.js` `gamejs.min.js` now put into gamejs home instead of deep into skeleton remove api/doc - must be rendered by user
Group.remove always removed the last sprite in the _sprites array if called with an argument not in the group.
there is a distinction between ImageData class and the actual image data, which is contained in that class as property `data`. I confused those. Browsers accepted the raw data as ImageData but were throwing errors.
the a* docs now emphasize more that the passed points don't have to be two-elem arrays (actual points), but can just as well be strings or any other object. as long as the Map.hash(), Map.equals(), etc. functions can operate on the point type.
i will in a following commit ignore it. it will only be present in gamejs releases but not in the git development version. if one wants to work with the git version, this file has to be rebuild. it's just to messy to keep it updated all the time and hopefully convinient enough to have it pre-built in a release version.