Today I spent mostly creating blog site for Crystal Kindom and fixing some bugs. Blog can be found here - crystalkingdom.net, let me know what you think. ;)

As I promised, here is a very early version of Crystal Kingdom for you to see how current AI works and maybe suggest some improvements and leave feedback. Hope you like it. :)
Click here to try it out
(You need Unity Web Player to play it).

Yesterday's update can be found here.
In a case of any questions or suggestions, don't hesitate to contact me here or on twitter. ;)
For more updates, you should follow my twitter account - @PeterLauris and the account of Crystal Kingdom - @CrystalKingdom_.

The project is basically to bring a Ruby Rack Sprockets like assets serving. It's nowhere near ready, but some things are starting to work. I wrote a couple helpers for the html/templates to insert <script> & <link> tags. The basic asset lookup and serving is now working as a Negroni middleware. Currently, it offers no advantage over the provided Static middleware, but that's because the asset processing & caching isn't written yet. I'll provide a teaser of the html/template helper.

I still have some concerns with talking about a project like this when it's this early in development. The biggest one is for anyone getting any sort of expectations. I don't really want to get anyone's hopes up that this is going to be great or usable. I really should stick with projects like this, but often feel like I get developer ADD and jump to another new/interesting project.

Some things I'd like to see eventually make it into this project:

1. Processors. Initially, it's going to be pretty basic. It'll use the Rails javascript require syntax for loading other javascript files to server more than one in a go, but it's not going to (initially) support any sort of minification, coffeescript compilation, SASS compilation, etc.
2. Caching. This very closely relates to #1, but will likely be rudimentary put into place before #1 (because it's easier.)

I've been out most the afternoon but I got a lot done in the morning and a bit done tonight. I cleaned up my lexer so that it finally processes CSS selectors and keywords properly. This had to be done in preparation for the next feature I want to add to the language, enums!

As I'm building a site and making up features as I go along, I realized I needed a method to easily manage global constant variables. I decided on enums as I always liked the concept of putting a few constants inside a neat little namespace.

Adding enums will require me to rethink how my current compilation of expressions works, as scope matters more than it did in the past.