caseywebdev

I've had my topcase replaced and the problems just came back months later. Does anyone know if they have a solution to this problem or is their plan to just have me ship my machine to them every six months and avoid the class action?

One advantage is that the planck [1] is over 4x smaller than the emscripten build [2].

[1] https://github.com/shakiba/planck.js/blob/master/dist/planck...

[2] https://github.com/kripken/box2d.js/blob/master/build/Box2D_...

I love that you kept the tried and true Box2D API as that'll make porting what I'm working on much easier. I've been using the emscripten version [1] but the automatic port from C++ makes the JS API quite painful at times, especially with the manual memory management that's required to prevent leaks. Thanks for doing this!

[1] https://github.com/kripken/box2d.js

For my React peeps looking for something similar, check out http://devblog.orgsync.com/react-list. Repo at https://github.com/orgsync/react-list

such as changing data in sibling components

[Cursors] can help a lot with this problem. As far as sibling/child components know, they own the state, but they're really using immutability helpers to update a larger encompassing state object.

[Cursors]: https://github.com/caseywebdev/cursors

I'm a fan of [superagent] for AJAX. The React lib is big, but its declarative nature has lead to fewer and easier-to-diagnose bugs for us, which is ultimately a win for the end user. I've been using it exclusively on new projects for months now and I'm a Backbone.js core contributor ;)

superagent: https://github.com/visionmedia/superagent

As of a few weeks ago my Cursors implementation correctly `shouldComponentUpdate`s path changes as well as value changes ;)

I went for a minimalist implementation that leverages the work done in React's Immutability Helpers (http://facebook.github.io/react/docs/update.html). The API allows you to use the same `this.state.xxx` you're used to which I find nice.

Unfortunately it looks like screenshots can't be edited (or even rearranged) until a new app binary has been submitted. I'll make this change when I get some new levels cooked up.

That's a good point, makes me wonder if the main menu screenshot is even worth showing.