= Jaws - HTML5 Javascript web game development library {}[https://travis-ci.org/ippa/jaws]
Depends on JavaScript Edition 5. Works with Chrome 9+, Firefox 3.6+, Safari 5+ & IE9.
Licensed under LGPL so you're free to use it for commercial projects.
== Highlights
Jaws also:
== Install $ bower install jaws
== Local build / test npm install npm test
== Learn more
== Tutorials
== What kind of games can you make with Jaws? Jaws is well suited for "classic" side/top scrolling games (tile based or not) where you have a number of sprite-sheet-animated sprites. Jaws comes with basic rect-vs-rect/circle-vs-circle collision detection that works well in most cases. If you have tons of sprites (for example, a bullet hell schmup) you probably want to use a physicslib like Box2D or spatial hashing like quad trees to speed things up. Jaws use of canvas makes pixel perfect collisions and worms-style terrain relatively easy to develop. If your game is very GUI-heavy you might want to base your game on pure HTML-elements instead of canvas-sprites.
== Simple examples demonstrating certain features Check out the sourcecode for comments and explanations:
== Games using Jaws
== Libs using Jaws
== Loading Jaws
You can also link to invidual files in your HTML:
NOTE: core.js is always needed but after that you can pick and choose depending on what you need. A rule of thumb is that a file named "foo.js" will include a constructor named Foo().
NOTE #2: jaws.js and jaws-min.js does Not include files from src/extras-dir. Examples of files that aren't included in the mainbundle are: tile_map_pathfinding.js, pixel_map.js and audio.js (jaws
== Contribute Jaws accepts contributions, some simple guidelines:
Jaws has gotten bigger contributions from:
https://github.com/videlais - QuadTree() and other things https://github.com/dmitrizagidulin - SpriteList() rewrite https://github.com/gregmax17 - Viewport related stuff https://github.com/MalphasWats - Viewport pathfinding
== Issues and bugs If you find an issue with Jaws githubs issue-tracker is the place to go. Easiest for the developers is if you put your game online. If you don't have any hosting check out http://pages.github.com/. Pasting your problematic code in the issue-ticket itself will usually mean a lot of hassle with supportcode and assets to actually be able to test the code in question.
== API-deprecations leading up to ver 1.0 2013-09: Remove experimental, buggy DOM-sprite-support from Sprite and Text 2013-08: SpriteList is no longer included in jaws(-min).js bundle, better off using arrays and jaws.draw/jaws.update 2013-08: jaws.assets.loadAll() - onfinish -> onload, onload -> onprogress 2013-08: jaws.assets.load(asset, options) - options can have properties onload and onerror 2013-03: sprite.anchor() is now sprite.setAnchor() 2013-03: sprite.scale() is now sprite.scaleAll()
== Example
== The same example with comments /*
so we can get straight to get game logic. */