Today was my first "real" day. Sure I'd been over to work last week too, but that was not a full day and I spent a lot of it just getting set up. Plus I worked mainly on my thesis research (as I said before, we're going to continue that a little).
But today I worked a full day, literally nine-to-five, on the DIAL project. I'm still very much in the "how" phase; I'm just trying to figure out how I'll be doing it. Even the implementation platform isn't set in stone yet (I'm trying my best to get them to let me do it in .Net :) ).
One thing that I do know is that I need a way to communicate with the server, and so far that can be done in four ways: via the Perl modules, via a command line interface, via a web interface, and a YAML interface. Since my stuff won't necessarily be running on the main DIAL server the first two are out. A web interface that tries to communicate with a server through another web interface is too weird even for my tastes, so that leaves YAML. A brief look at YAML didn't reveal any problems with this.
Unfortunately, a detailed look reveals more than a few problems! For one thing, good YAML parsers are scarce. Really the only decent ones I could find are for Perl or Python. There is as far as I can tell only one parser for .Net and it doesn't work properly. That means I have two options: roll my own parser, or convince the DIAL guys to give me a different interface.
Since the YAML spec is very hard to read, and YAML in general is extremely hard to parse (it's designed for human-readability, severely compromising machine-readability), writing my own parser wouldn't be fun. The grammar for YAML is context-sensitive, determines scope by indentation, and has far too many ways to do the same thing. I could decide to limit myself to the subset of YAML that the server seems to be using, which makes it slightly more possible, but it's still not my first choice.
That leaves trying to get a different interface. I've briefly looked at the DIAL code, and the YAML generation is pretty much a matter of calling YAML::Dump from the YAML CPAN module. Which to me at least makes it seem like he could pretty easily use the XML::Dumper module instead. Here's to hoping.
Vista style file dialogs for .Net 2.0 is a library that allows you to use the new common file dialogs available in Windows Vista with your .Net 2.0 applications (the regular FileDialog classes will use the old-style dialogs even when you're running in Vista). See here for more details.
I've just uploaded version 1.2 (for those of you keeping track, yes I skipped version 1.1; I used this version myself but never uploaded it).
Here's the changes:
Since I wrote the blogging engine used by this site myself, it lags a bit behind some other blogs in terms of features. I specifically chose to do this though since it allows me ultimate control over the look and functionality of this site, and give it a few unique twists (for example: there are, as far as I know, no off-the-shelf blogging engines that do the AJAX comment loading and calendar that I have here).
I've been working on getting some of the gaps filled. In the past week I've added post categories and more friendly URLs for the individual post pages. Also new is that the calendar now shows the number of posts for that day if you hover over a link (it's rarely more than one, but still). I've also fixed some bugs and improved the code in many places, which should make for a better experience all around.
El Goonish Shive fans will be pleased to know that I have begun work on catching up with the character statistics. I'm hoping to get that done this weekend, before I get swamped in real work again.
Subscribe