21–27 of 27 posts
What is interesting to me is that the concepts in the article are arguably more valuable the sample code itself. But by charging for the shallower of the two assets, you end up charging the people who are more likely to pay in the first place.
This is great, the idea of deconstructing well known games as a teaching method is pretty cool. Knowing the effect that you are hoping to achieve while reading the code really helps in understanding the implementation. Very nice, keep them coming :)
Slightly on a tangent, but some may find this interesting. Super Mario World Camera Logic Review: http://www.youtube.com/watch?v=TCIMPYM0AQg
The thing I found most surprising was at the end when he was able to go off the screen by going backwards which very much seems like a bug in their algorithm, but maybe "it's a feature".
That game definitely has good camera management though. I never sat down and thought about how elaborate their scheme was.
There is a new article in the works as well; stay tuned :)
Earlier quoted context omitted.
Why do you say so? Aside from sound (HTML5 audio is a poor fit for in-game sounds) what is not good about it? Especially with canvas getting hardware accelerated in IE9, Firefox and Chrome and WebGL getting ground in more browsers (Chrome, Firefox and now Opera Alpha). EDIT: to be clear, it's genuine question, I'm really interested in high-performant graphics in HTML5.
Aside from doomlaser's answer, have you seriously seen a single demo in HTML5? As I've not seen one yet that doesn't stutter or crash. Even in Chrome with v8. HTML5 is like 5 years behind Flash in terms of performance. Also writing in HTML5 at the moment is like being given the total basics. Canvas, as an API, sucks. It'll get better, more libraries will come out, but god-damn it feels like moving backwards to take a…