Javascript game engine for jQuery
gameQuery is a jQuery plug-in to help make javascript game development easier by adding some simple game-related classes. It's still in an early stage of development and may change a lot in future versions. The project is hosted on GitHub (it was hosted on Google Code before) and a twitter page where you can follow the daily progress of the development.
If you have any comments, bugs to report or suggestions you're welcome to send an email to: gamequery(at)onaluf(dot)org or use the Google Group. You can also leave a comment the gameQuery entry of my blog.
Get the latest version of gameQuery:
Goals and Features
gameQuery tries to:
- be easy to learn and use
- stick closely to jQuery philosophy
- be fast enough on most modern browsers
- allow a beginner to write a rich 2D game
gameQuery has the following features:
- multi layer-sprite animations
- sprite hierarchies (grouping)
- collision detection
- swappable sound support
- periodic callbacks
- keyboard state polling
- free and open source license
Latest news (more)
13 June 2010:
At last, 0.5 released, with a nice tile-engine.
25 December 2009:
Brand-new website and 0.4 release.
14 December 2009:
Since the answer to the poll were largely in favor of the refactoring I did just that. Those are the changes to come in the next release:
- Moved
Animation to the $ scope. What was new Animation(...) is now new $.gameQuery.Animation(...).
- Sound interaction are now abstracted to a
$.gameQuery.soundWrapper. This is a swappable piece of code that handles sound bind to an custom (HTML5) or existing library (SoundManager, jPlayer).
- New .playground() behavior, more jQuery-y: you should now write
$('mynode').playground({...}) instead of $().playground('mynode', {...})
- Sprites have now a geometry attribute that describe if there are rectangles or circles. This is used for collision detection. (for now only rectangle are supported)
Those changes are already in part present in svn if you like to test them. For the rest you can expect a release in the weeks to come.
27 July 2009:
I'm considering the possibility of breaking the API in some parts and I need you advice about that. Please take some time to answer the poll
here.