Over the past couple months I’ve been working on an object oriented HTML5 game engine known as Canvas Prime. What makes it very different from all the other Canvas game engines, is you can use simple hooks to significantly modify the engine on the fly. Want to rewrite collisions at the engines core? Use a hook. Want to rewrite the loading screen animation with the current load value? Use a hook. Want to add in WebGL models, could easily be done by adding in a couple hooks.
For a long time I’ve been searching for a perfect set of test content I could drop into any WordPress WYSIWYG. Reason being its a pain to go through and use every single TinyMCE item to test a theme. To make matters worse, you’ll need to upload a ton of images or reuse some multiple times. Because of these issues, I’ve created what I feel is the most efficient way to test out the WordPress WYSIWYG.
Looking to use WebGL for Internet Explorer? If so, you wont be able to without IEWebGL. This new library allows developers to support a majority of WebGL’s features in IE. Oddly, all major browsers except IE now support WebGL. Which begs the question “Why doesn’t IE support WebGL?” Since this is a complicated subject, I’ll sum everything up as briefly as I can.
Tonight I was trying to install Node.js on Windows and couldn’t find any straightforward documentation. Reason is each new release of Node.js has multiple ways it can be setup. For instance, older versions required Cygwin and some people use a .exe file. None of these methods are optimal, so I’ve written a tutorial on how to install Node.js own Windows and test it in 6 steps with less than 10 minutes of your time.
WordPress’s Twenty Eleven child themes make great use of HTML5, but suffer from one particular flaw. They require you to hack apart functions hijacking your code in unexpected situations. Because of this, I’ve created a Twenty Eleven child theme shiv that removes all the extra junk, so you don’t have to worry about manually cleaning everything.