Progress – I can make moves. Okay, so the timebank isn’t working correctly, my board seems to have some problem that means when black moves it creates errors on the WebBrick server, and you can’t take a piece that is causing check, for some reason, but I can sort that. It’s good progress though!

So, I’ve been a bit busy with things, so I don’t have any of my usual interesting links to post. I’ve been getting stuff done with the Rails Xiangqi site that I’m building (Chinese chess to the rest of us). Nothing radical, just plugging away.

My biggest complaint with Rails so far is a lack of books and documentation. I mean, the API docs are pretty good, but I’d like to see more example, more tutorials, and a structured thing like a book would be wonderful.

So, what have I learnt? Well, I’ve used routes.rb to set up the default page for the site. You can also ditch that index.html file from public in your application too. I think I’ve figured out how change passwords in the security thing, which is a bit involved, so sometime I’ll post the code.

Partials – annoyingly – don’t have a ‘general’ folder. You can create one, but you have to specify it each time you call a partial. That sucks a bit.

I built a lot of the user admin stuff – login, signup, etc.. It was made very easy by the Login Generator. Updating users and stuff – well, that was only a slight change to the normal scaffold. The big change was updating the password – but even that wasn’t too bad.

All in all, still impressed by how much you can get done in a short time with Rails.

One thing I’d like to figure out is how to do a persistent Login cookie for Rails. I don’t mind having my session deleted, but having authenticated that user, I’d like to not have to do it again the next time they visit the site.

Long time ago I wrote a Java engine for figuring out valid Chinese Chess (Xiangqi) moves. I was going to build it into a website, something like Red Hot Pawn. Well, it seems that Ruby might be much quicker to develop the database and presentation parts of a website, so I decided to port my Java code across to Ruby. It was very easy, both being very object oriented. It works just fine. Now, all I have to do is the site itself – which should be quick in Ruby.