Some of you likely noticed that around late Thursday of last week, in conjunction with my lengthy post about my adventure into canning this blog went wonky and showed something that was an incomprehensible mix of two posts. The good news is no one wrote or commented telling me my writing had improved.
I think the problem had to do with using BlogJet. It seems to support dasBlog nicely but something went horribly wrong. This post is using ecto. I so, so so want to like ecto, and I do it's got that perfect mix of raw dork horse-power ( html-templating with keyboard short-cuts; solid html generation; and flickr/Amazon/YouTube buttons). But, and there always seems to be a "but", it was barfing on a post I was trying to make again my humble little dasBlog instance. I attempted to debug into the code on the dasBlog side, a big reason I chose dasBlog. In my initial look through I concluded that the problem was likely somewhere in ecto, not that dasBlog is a shining example of good code practices.
I know, I know dasBlog is open source and I'm so critical, why don't I roll up my sleeves and dive in? The truth of the matter is, I'm not interested in writing a blogging engine, or even really fixing on this one. I've got other side-projects I want to work on and the list is already too long. While I don't believe blogging is fully mature, the issues I've been having with what seems to me a late teen set of technologies: blogging APIs and blog software) frustrates me a bit. And maybe this problem lies in the technology I've chosen. Blogging comes more or less from the PHP side of the tracks and .NET being my comfort zone I opted to use a .NET open source tool. Maybe it's time to learn PHP. (You hear that Bill?)
Back to the dangle-y loose thread holding this post together. I won't be using BlogJet on a live instance without further testing. Windows Live Writer (thanks for the suggestion Ben) hasn't really gotten a workout from me, will be making an audition on a laptop near me. And ecto, oh ecto... What am I to do? I went to your help page hoping you could tell me how to tune your software for dasBlog and this is what I saw:
Looks simple right? You'll notice I've included both the left and right edge of the browser window in the screen shot. In fact, I even went so far as to view source - there isn't an input tag on the page.
I'll give it another try, cause I like it so much, but it looks like Windows Live Writer might win. While it was fun to do raw HTML and I like the spell check and ability to have drafts of future posts.