This week I've made a lot of progress on rails' JavaScriptGenerator. JavaScriptGenerator basically offloads a lot of the work to the underlying prototype js library, and it's meant to be an expressive means of speaking javascript with ruby code. To maintain this flexibility, I've been implementing a lot of prototype functionality in our drails javascript package.

There are 2 new classes, drails.Element and drails.ElementCollection, and one new interface, drails.Enumerable.

Not much to report this week as far as actual commits go. Been working on grokking rails' JavaScriptGenerator, JavaScriptHelper, and PrototypeHelper. I'm hoping to have a dojoified replacement for the aforementioned done by next week. I'm working on rewriting the unit tests from rails to their dojo equivalents right now, then moving on to the implementation. Stay tuned for updates.

So this past week I've been working on a new data flow for our d-rails helpers in rails. I've implemented most of the dojo.fx functionality with this new flow, since it's a relatively small subset of functionality that would give me a pretty good idea if this was going to work well or not.

So let's start.

Ahh, it feels good to come back from a much-needed week long vacation following final exams. I know you all have been wondering what I've been up to, aside from enjoying my time in the sun and drinking margaritas. So for d-rails, the word of the week this week is testing.

Hi guys, my name is Jon and I'll be working on giving dojo a stronger foothold in the rails community for my summer of code project. The project I'm working on is called d-rails, and its goal is to make it easy for rails guys to quickly get rolling with dojo and add rich client-side functionality to their applications with minimal effort.

I know there are probably more than a few rails users out there in our community, and I'd LOVE to any and all ideas you have for the project. Shoot me an email, jmoeller (at gmail), and I'll happily take your suggestions with open ears.