This is a test using FireFox instead of BloGTK.  It is nicely integrated with the browser and, mirabile visu, it is a WYSIWYG editor.

Of course, it also doesn’t integrate properly with drupal’s input formatting so what I can see as I type appears on the web as literal tags!  I would have to go in and change the input formats for the message to get the correct display. Now, there is a way to get a blog client to set this using some obscure variable, via the rpc; however, I don’t think performancing will do this for me. It may just be possible to embed a code in the body, but I don’t know the protocol well enough for that.

Input format is a bit of a misnomer — drupal saves the unaltered text in the database and transforms it each time the page is rendered — so postprocessing isn’t as onerous as it sounds.  It does add an unnecessary step which a blog client is supposed to paper over.

Hmm, I accidently saved two versions of a single post.  Clearly I pressed the wrong button.  Let’s try again.