javascript game development made easy
Documentation
Here you should find all the information you need about gameQuery. If you don't you can contact me at: gamequery(at)onaluf(dot)org.
- API: The complete documentation of the objects and functions provided by gameQuery.
- Sound Wrapper API: Sound Wrapper specifiaction and how to use them.
- First Tutorial: An introduction to game programming with gameQuery by the example of a simple side scrolling shooter.
- Migration Guide to 0.4: A small migration guide from 0.3.x to 0.4.x that should make upgrading rather painless.
- Release Notes: Wanna know the differences between successive released? Have a look here.
FAQ
How can I help?
You can contribute code to the project, write a game with gameQuery or simply speak about gameQuery on your blog or tweet about it. Don't hesitate to rate the project on it's jQuery plug-in page.
Who is behind gameQuery?
gameQuery has been created and is still being written by me, Selim Arsever. I'm a computer engineer living and working in Zürich, Switzerland. Being an open source framework it has beneficiated from the feedback of many friendly user and you to can contribute!
I've done everything just like you told but nothing happens!
Did you call the startGame() function? Usually this is the cause of your problem if you don't have any errors on the javascript console.
There is a bug in my gameQuery!
Well sorry, I did try my best... Don't hesitate to fill an issue on Google Code
What is the point of making games with javascript?
Javascript games are still in their infancy but but there is many reason why they are more than a curiosity: Modern borwser provide very good javascript engine and impovement keeps comming. Then to develope javascript games you don't need an expensive proprietray IDE, widly available, free, open source software are there wating for you! Sometimes Flash is not available in some platform, even very recent ones (Wii, iPhone ...).
Why using DOM instead of canvas?
Canvas is a very powerfull and efficient way to maniputale images in the browser and is thus probalby the best solution for nice looking games, however I choose DOM manipulation for gameQuery... why is that? First I think that for most practical solution ouside of games DOM is still the way to go. Since one of my goal was to learn usefull javascript using DOM made sens to me. Benchmark for pure javascript are available but aving a way to test the DOM engine is more tricky... games are a good way to test this side of the javascript performances. Finally I hope that gameQuery can be used by beginers to learn game programming and with this in mind I think it's easier to debug you games when all your object are visible with a simple DOM explorer.