Javascript Framework for 2D Game Development - GameJS
tommysmind.com
tommysmind.com
I worked on this several months ago and never really had a second look because of lack of time. New job and all. I always wanted to come back to this though and polish some stuff like sound support (would have to be flash i guess), mouse support, some optimizations (did some tests creating space invaders and found some very real possible improvements, by for example using the experimental canvas.drawString available in some of the nightlies of (proper) browsers), and some other minor quirks.
If anyone has any questions or just wants to discuss something with me about the internals or possibilities, you can contact me at tommy@extjs.com
Still a work in progress, but it's the first thing I've written in JS.
You're mistaken that IECanvas will make your game slower in IE than it is in Firefox. Test it out, and you'll be surprised. IE has a much better rendering engine than FF, and even with the added overhead of converting all canvas calls to their SVG equivalent, it's still noticeably faster.
So yeah, please fix your thing. It's one line of HTML fer cryin out loud!
(nice effort, by the way)
I have some experience with this -- my site uses canvas / ExplorerCanvas quite a lot -- ExplorerCanvas is both buggy and extremely slow for any kind of animation. Particularly long running animation (as in games). I wish it wasn't so.
VML may or may not perform well, but it's a different kind of api than canvas. In VML, like SVG, you're intended to draw a bunch of shapes and then manipulate them. To animate a circle crossing the screen, you draw the circle and the move it every tick. The library manages the redraws, etc.
With canvas, you redraw every frame. So, to animate that circle you draw it in a different position every tick.
If you run canvas on top of VML you end up redrawing a lot of extra elements which get reinserted into the dom at every step.
They're just fundamentally different approaches and the impedance mismatch kills ExplorerCanvas's performance. If this has changed recently, btw, I'd love to hear about it!
http://www.twiddla.com/demo/rendering-performance-canvas.htm...
On my machine, IE will render 170 boxes per second. Firefox bogs noticeably after a couple seconds and finishes at around 60 boxes per second total.