Spent about an hour prototyping combat in my game (Murder with Friends). Nothing too taxing, but still productive.

Today I finished off a refactor of the initial smattering of ideas I've played with over the last couple of months. This brings my code into line with the architecture guidelines for the language I'm using (http://elm-lang.org).

Further to this I fixed up the issues rendering the basic isometric tiled map and began on building the map editor.

Work continues with the joys of NodeJS on a RasbPi.

Making progress but its slow with lots of steps backwards.

I got stuck mostly in setting up environments last night. I thought I hadn't really done much with my FIGnition yet, so I'd plug that in and go. It didn't take long to realize why I had been slow to really get full swing with it, QWERTY default. FIGkeys seems to allow most keys to be remapped, but requires a number pad. I decided to wait until tomorrow to get a PS2 or USB keyboard with a number pad.

Then I decided to get my BeagleBone Black setup. I tried Cloud9 a bit, but then decided to install Go. I forgot there weren't pre-built Go ARM/Linux packages. I pulled down Go from git, checked out the 1.4.1 tag, and started the build. When I realized it was going to take some time, I went on to the next thing.

Next thing was playing with the Launchpad some more trying to load mspforth, CamelForth, & Mecrisp, all without much luck of getting a serial connection. One thing that stuck out to me was that newer Launchpad boards potentially changed the USB serial pins. As a last ditch, even though none of the Forths seemed to support it, I fired up my new MSP430F5969 Launchpad, but Energia said I needed to update the drivers, which failed on Linux. Had to download a tool from TI that appeared to repair it. Tried again, and the update failed again. After repairing a second time, I decided to call it a night.

Overall, I didn't touch much code, but I did a bit with MSP430 assembly with naken_asm => msp430-gcc conversion, but nothing really worth posting.

Today I started learning Node.js using the "Node.js in Action" book. I created a small chatserver (standard nodejs tutorial, haha), and so far it seems pretty interesting! It's clear to me why it makes such a great tool for building servers, its event-driven loop lends itself well to the task.

Not much was done today, I made a start on code generation and the HTML and CSS generated is looking good. Unfortunately attributes defined in the components aren't being passed across to the code generation system properly but I should hopefully have that rectified by tomorrow night.

I'm hoping that far into the future when everything is at an acceptable level, building a website will be simpler with better error reporting. ie. If you set a min-height on a <table> element, it tells you off. (Because as everyone knows, <table> only accepts height and height acts like min-height)