I’ve posted many entries about WLW. But now that version 1 has been out a while I thought I would add my latest observations.
- The deferred posting mechanism just doesn’t work. Posts just don’t get posted when you tell them they should be (true in WordPress 2.x and Blogger, so far as I can tell). This isn’t a huge issue – but it is a feature I’ve learned to avoid. Even pulling up the calendar and NOT changing the post date/time causes the post to not get posted when submitted. Something appears very broken here.
- The “Insert Video” function isn’t near as clean as say, cutting and pasting embed code from YouTube. WLW is adding something to the video when you use the “insert video” tool that causes my theme to get very broken. Pasting the embed as a raw HTML doesn’t cause these issues. So I don’t think it is my theme. So I avoid this feature and switch to raw HTML editing when I need to insert a video.
- I post on nine different blogs. I would really like the option to have WLW remind me that, “You are posting this to Stuffleufagas – continue?” Of course this would never appear if you only had one blog configured in WLW, and it should be able to be shut off. Believe me, it would be VERY embarrassing to post to the wrong blog!
- Because I post on a number of blogs, and I use a number of machines to do it, WLW should not just store my settings locally. I have a Live! account. And an Internet connection. Store my settings in the cloud somewhere and let me retrieve them via my Live! account.
- Build a web based version of this tool. Now! 🙂 Really – a rich web application that did what WLW does would be a killer application for bloggers. And I really wouldn’t even mind if you ran an ad or two on the page – as long as it stays out of my way. I HAVE to believe this is already planned, if not already under development. The old Onfolio team is too bright to have not thought of this.
- Change the image defaults to add margins of 5 all around. I can always tell a blog post that was made with WLW in the default picture margin mode. The text is so close to the image it is almost unreadable. No reason not to set this as the default since it can always be changed by the blog owner.
- Get MUCH smarter about errors. Don’t just tell me that there was an error putting up a post. 99% of the time WLW kicks an error the post still is posted. So what was the error? Perhaps in many cases the development team just can’t tell. But in the case where they do throw an error they could then go back and read the latest post on my blog. Is it the same post that I WLW just reported an error on? If it is, assume it worked (because 99% of the time it did). Save the post locally, and let me get on with things. “Ghost” errors are the biggest single issue I have with WLW. And even when the error is real, I have no clue what caused it. Start a “Windows Problem Reporting” style database for errors. If you learn a specific plug-in causes a specific failure, then tell me. I can do without almost any of my plugins before I can do without WLW (except my Spam Karma 2 plugin – but then, you could build a Windows OneCare blog plugin and take care of the spammers for me)