city41 / reagent-breakout Goto Github PK

These examples pretty much say it all. Will make the event handling cleaner and more powerful.

Should probably also be able to add only one click handler and one mousemove handler for the life of the game

Add sound effects, they are located here

Need the CSS to be responsive so that on a mobile device only the game is seen.

Need to hook into touch events to move the paddle.

Hi,
I'am currently looking around for a nice game engine for some side project. I've been playing with react for some time and really like the whole concept. Being able to use it in a side project would be incredibly helpful to learn it better.
But I'am wondering if react is the right tool for creating games (in fact, I sincerely hope so) and what i'll loose compared to an established game engine like phaserjs, melonjs, etc. Maybe using react (and flux) for the whole architecture and passing the animations/rendering to something like snapsvg might do the trick.

This is not really an issue, I just want to hear what other, more experienced people, think about this. Most of the game examples are pretty basic but I have something RTS-like in mind, which is quite a different scope i guess. Any advice/recommendations you can give?

stop the madness.

Already forgot to add FF animations for the countdown, and there are no IE animations at all.

Currently when hitting the paddle the y velocity is deflected and that's it.

The velocities need to alter depending on where on the paddle the ball strikes, allowing the player some control in the direction the ball goes.

the primitive hit detection isn't cutting it. Not sure how far I want to take this, as this app is really just a proof of concept.

The hit detection algorithm only accounts for certain situations, and so often the ball can just plow through bricks.

The ball is animating itself with setTimeout, this only works correctly the first time a ball is added. Need a more general approach.

Currently if a brick is hit, the ball deflects in both x and y. It should only deflect in one depending on which side of the brick was hit.

currently ball movement is hardcoded to 2 pixels per frame. It should take framerate into account and use delta to move the ball in a framerate independent manner.