Game Development Tutorials

Fancy making a game? Using Canvas? You do! Excellent!

Matthew Casperson has been incredibly busy writing this whole bunch of tutorials about developing a platformer using canvas. From keyboard input to parallax scrolling, from animations to resource loading – it’s all covered in his tutorials.

Jump, run, jump some more.

Jump, run, jump some more.

Check them out here:

Info

Type:
Intermediate, Tutorials
Author:
Matthew Casperson
Posted on:
July 9th, 2009
Posted by:
Andi Smith
Views:
14998

Rating

4.94

Your Rating:
1 Star2 Stars3 Stars4 Stars5 Stars

Works on

BETA Please let us know if you find Game Development Tutorials works in other browsers by leaving a comment below.

Comments

jack

really cool
thanks

Posted on April 29, 2010

TwFlash

Hi, It’s a really cool work you made here. I think i’ll study your sources for my firsts self teaching HTML5 canvas JS sessions.

But… When i see JS… Oh, it is so an ugly language ! What a pity I feel I have to to learn this… Thing. What a pity some people saying it could be compaired and better than flash AS3.

I’m so sad with this HTML5 thing, wich will take us so many years back (I speak in the coder point of view, ok ? I know how cool the idea of HTML5 canva is. It’s just… The wrong language for it.)

So, if we have to… Let get to work, I have so much to learn !
But Flash is better to do games, API and animations, and i’ll go on screaming this as long as I can.

Bah… Maybe, one day, JS will be full Object oriented, with decent constructors, clean memory handling ? ;)

Posted on May 2, 2010

TwFlashHater

A bad language for it? It’s a bloody brilliant language. Point out to me one reason anyone would not want to code in Javascript.

Posted on May 4, 2010

TwFlashHater

It’s a fully prototype-based object-oriented that allows for runtime composition of objects. What constructors, which planet are you from? Prototype-based languages have no concept of classes.

Memory handling? What’s wrong with its “memory handling”? Sounds like something you picked up in the PHP manual. “Yeah, memory handling sounds like something that would impress chicks at a bar”. What are we coding, C, and dealing with retain counts and pointers? Which modern high-level languages out there even let you touch memory management?

Eesh.

Posted on May 4, 2010

TwFlash

Well…

“Prototype-based languages have no concept of classes.” :

- this makes harder for me to organise my code. Where are the packages ? How can i make my functions to be private or public ?
- using patterns is more difficult in JS…
- I feel that JS coding pratices dépends on each coders, and less on the language itself, so my code may not be easily read by another guy who will go on my work. And it’s harder to make UML charts. And harder to work in teams.
- prototype inheritance is not good enougth. You can only simulate OOP features (and this is sufficient for many works). When you are used to use inheritance from classes, it’s very disturbing to use JS.
- But multiple inheritance simulation could have some cool use.

“Memory handling? What’s wrong with its “memory handling”?” “Which modern high-level languages out there even let you touch memory management?”:
In fact, I was talking about Garbage Collector. And here I was wrong ! But in AS3, the GC handling is easy. In JS, this seems more complicated. I’ll see that later !

There are one other bad point for JS : portability of the code on browsers and mobiles… Eeesh.

I try to be objective. Flash has some flaws too !

I’m sure i’ll make some cool things with JS and the Canva. I’ll just be a little more limitated than doing them with Flash and AS3.

Posted on May 4, 2010

AnotherFlashHater

I’m still a noob when it comes to web programming, I’m only just completing my first point-and-click game in pure Javascript and I don’t know ActionScript, but you also have to look at it from a user’s point of view: flash is slow, it often blocks the browser, it doesn’t run smoothly on all systems (support for Linux is quite crappy), you can’t even use bloody F11 to toggle fullscreen once you’re inside, because it’s so much separate from the browser and from html. And last but not least, it’s proprietary and closed, which makes it a bad choice for the future of the net. The less we become dependent on one company to provide web content the better.

Posted on July 28, 2010

Add comment

(required)
(required)
(will not be published)
(required)