Earlier this morning I noticed this post by Mena Trott on Six Log about an update to Kung-Log for Movable Type version 2.6. And I’m thinking, “Why didn’t I know about Kung-Log before now?” I guess I don’t get out much. But I did get Kung-Log then and started playing with it.
The funny thing is that not minutes before seeing that post I was underwhelmed with the support of Movable Type’s features in NetNewsWire’s “Weblog Editor” and I realized I might be stuck with Movable Type’s web-based interface to do all my blog editing. Now I really like Safari but a specialized editor is always better for things like blogs than a general purpose tool like a web browser.
Kung-Log was fairly easy to configure but too bad it can’t auto-discover your blog’s XML-RPC URL via RSD like NetNewsWire. Then again, if NetNewsWire supported the extended entry field or most of the other cool Movable Type settings I might not have even tried Kung-Log.
What can I say about the rest of the user interface? Whenever you title a menu “Special” then you have a UI presentation problem. And the default set of toolbar buttons won’t fit on my iBook’s 1024 by 768 pixel screen with the “Recent Entries/Drafts” drawer open.
Where is the menu or keyboard command equivalent of the “Toggle Entry Settings Drawer” button? Without other access, I’m stuck with leaving that button and its huge title on the toolbar. And most of the other button titles are too big as well.
Often when I changed templates in the “Edit HTML Tags” window I had to restart the application to get them into the “Insert HTML Tags” menu on the toolbar. Something isn’t working correctly there. But it’s not like Safari doesn’t have bugs either.
Still, Kung-Log does integrate well with Movable Type. And it works as advertised. At least for re-editing an existing entry. I’ll find out how it works with a new post when I’m done writing this one. But I’m guessing that a PayPal donation will be following shortly.
Adriaan Tijsseling, Kung-Log’s author, indicates he wants to use Safari technology to replace its current HTML preview implementation. What an excellent idea. I’ll have to send him an SDK when it becomes available this year.