This blog, over the past few months, seems to have veered broadly, looking rather more at the context we operate in--and less at the detailed progress of online, interactive, sound-and-animation history telling.
I'm going to try to change that focus back. The best way to do that is to get more developers involved. We've always intended this, of course, but have balked for reasons having to do with - in Kipling's great phase, 'a deficit in the budget'.
Meanwhile, this week I've been looking heavily at Ruby on Rails. If you say, 'egads, no, not another programming language!', we won't blaim you here. 'Twas exactly my reaction a year ago. Butrubyisdifferent. I'm not a programmer, so I'll leave it to you to tear the language apart. I have, however, seen the promises of some 30 languages along the way, and my week with Ruby on Rails tells me that building web applications just took a big jump from Php/HTML.
So, when we get a little better handle on Rails and Ajax here, we'll start searching harder for great interactive history examples. Meanwhile, head over to the wiki and see what you can add.