RSS Feed
May 3

I Love/Hate Windows Live Writer

Posted on Thursday, May 3, 2007 in Blogging

Windows Live Writer (beta)—Most likely the best local blog editor going. Or at least it will be in the final version whenever that may be. After months of using this exercise in frustration with all it’s excellent features and all it’s bugs and quirks I’m well past the point where I have to grit my teeth or at least sigh very heavily every time I open it up. It just does some things so well and a few other things so horribly. Now, I’m not going to do yet another review on all the wonderful features and bugs of this fine first offering by the Windows Live Team. There’s plenty of reviews out there already. This post is about what I absolutely have come to hate about this otherwise great blog editor.

So here’s a few things that keep me from using WLW full time. My love/hate list in no particular order:

(And all due respects to the WLW developers. I understand how it is however, frustration being what it is…)

I love how WLW works images:

All the basic functions built into the editor work very well from basic image placement within a post to adding a watermark to an image. Shadows, borders, embedded links and basic editing features such as sharpening, blurring, Sepia etc all work as you would expect and this Should make “time to publish” fairly short depending on the length of the post of course and it does with one glaring exception. See below in…

I hate how WLW works images:

One of the biggest complaints about the image feature of Windows Live Writer is that when you add a border to an image, it decreases the size of the image so that the border and image combined have the same dimensions as the original image. For instance let’s say you want to insert an 100 X 80 image into a post and add the “Photo” border around it. The problem comes about when you add the border. Once added, the dimensions of the image have now been decreased by the width of the border surrounding it making your once sharp, clear image pixilated and basically non-viewable and that isn’t something you want on your blog. The same goes for the drop shadow only the degradation in image quality is not as bad simply because the drop shadow effect is not as wide as the “Photo” type border and only surrounds two sides vs four.

The workaround of course, is to set the “Border” effect in WLW to “Inherit from weblog” and add your own effects to your image using your favorite imaging program before you insert it into your post. However, this type of sidetrack just adds that much more time before you can publish.

Hopefully this will be fixed in the ever promised new release.

I love how WLW handles publishing:

Couldn’t be simpler. Almost a one-button publishing function. In fact, unless you’re posting as a draft, that’s exactly what it is and publishing as a draft is just about as simple. Just use the down arrow next to the publish button in the toolbar and select it. Simple enough. The other thing I love is that the WLW’s publishing feature automatically knows whether the post is a new post or just an edit. No having to choose between between either a “publish as post” or “publish as edit” type of thing so none of those “Oh crap I published it twice!!!” mistakes occur. Works pretty slick. Well almost, as you can see below.

I hate how WLW handles publishing:

Images! Windows Live Writer murders images when publishing. Not the quality mind you. Not as long as you don’t add a border or drop shadow as I said above. No—I’m talking about two things here.

First, let’s say I insert an image into a post with the ingenious name of…image.jpg. Now, once I publish, I expect the name of the published image to remain…image.jpg. Logical yes? But noooo. To wit:

I insert…

“image.jpg”

…into a post called…

“Yet another post.”

Then I publish and what do I get for my image name?

“windowslivewriteryetanotherpost-10757image.jpg”

Ohyougaottabekidding! I have read that the original intent was to keep the uploaded images off the blogger’s root directory of their install and the above cobbled together name was actually a path to other sub-directories it created which was just as bad…such as:

“windowslivewriter/yetanotherpost/10757/image.jpg”

How or when the path changed to renaming the image I simply don’t recall and I no longer care. Could have been the last update to WLW (build 6) or could have been Wordpress 2.1 that did it…don’t know. I just hope it’s fixed in the new upcoming release.

Second, I can’t edit any post if the post in question has images. Why? Because with every edit I make and publish thereof, WLW uploads a whole new set of images for that post and slaps an additional number onto the end of the already garbled name for good measure. Edit a post with three images, three times and you end up with nine images total uploaded for that same post. Doesn’t bode well if your host limits your storage space now does it?

All these rants of mine have already been well documented by myself and others at the Live Writer Forum and are supposed to be fixed in the next release and this leads me to the final rant….

WHEN? I realize that this, almost seven months old release is a beta and for the amount of features there are bound to be a few bugs and…that the next release is going to be a major one but seems to me that it should have have been released like yesterday already!

Alright—got that out of my system but I have been faithfully following the forum since November, 2006 and all I ever get lately is that the new version will be released soon but they can’t say when. And I know what requests for new features aren’t going to be addressed in this release. Heck, I even know what it so in my mind it’s time to stop dangling the word soon in front of us hard-working bloggers and deliver the goods! Over a half a year is too long in my opinion.

Besides…I have a major undertaking I need to get started on soon and I want to use Windows Live Writer to do it and I want to use it without having to spend an extra 10 minutes each time I want to add a photo. Selfish? You bet!

There are other small bugs in the Writer but they aren’t going to limit anyone’s use unlike the ones I’ve already mentioned ever so delicately but that’s too be expected from a first effort. I just hope that the new release will be out before much longer. Like before it officially becomes summer?

Technorati tags: , ,

Share and Enjoy:
  • Google Bookmarks
  • Digg
  • del.icio.us
  • Twitter
  • Facebook
  • StumbleUpon
  • Sphinn
  • E-mail this story to a friend!
  • Print this article!

Possibly Related Matter

Bring on the comments

  1. Sunny says:

    I’m going to try WLW when I get off a shared computer here. I have a unrelated question. How do you allow commenters to edit their comments? Is it a wordpress plug-in, or somehow related to WLW? (nevermind – I just saw that you answered this on another post. the link is http://www.raproject.com/wordpress/wp-ajax-edit-comments/)

  2. KirkM says:

    @Sunny

    The WP Ajax Comments plugin has to be one of the all time greats. I feel that it’s really important to give something back to the readers who stop by and take the time to comment. Blogging wouldn’t be half as interesting without the commenters.

    If you check the tabs above the header there’s one called “Plugins I Use”. The page lists all the plugins I currently have in use on this site so if you are wondering how something happens or are just curious about what plugins someone else uses, take a look.

  3. becky says:

    Hi Kirk,

    I haven’t tried live writer beta 2 yet, but I appreciate your thoughts on the program.
    I think I need to do a ful restore of Vista first. Having a few problems with it (its a new install) so when I finish work later I am going to do a full reinstall to try and fix the bugs and then maybe look at the new live writer.

  4. KirkM says:

    Hi Becky!
    Glad to hear from you. I’m still pounding away on XP Pro. It’s been running pretty fair since my last re-install (two years ago? knock on wood). Perhaps when I get to the point where I can afford a new computer I’ll have Vista to play with as well. At this rate though it will be well past the release date for SP1 :P

    Be wary of WLW B2. It solved the old problems but released a whole new set of them, some of which I touched on in the latest post. Also, something I just found out…don’t use dashes in your titles (really). I had this horrible problem of any post written by WLW (beta 1 or beta 2 apparently) that has dashes in the title, strips out all the CSS styling in the single post page. Once I removed the dashes, everything was fine. I don’t know if this is just WLW, Wordpress 2.2 or a combination of both but it as driving me nuts and I just now found the solution.

    Let me know how the new WLW works for you if you could. The more bugs that are found the better the final will be and all that.

  5. KirkM says:

    Follow up:
    Nope, it seems to be Wordpress 2.2. Every post I had that had double dashes in the title (no matter what editor I used) stripped the CSS out of the single post page for those posts. Unfortunately I didn’t notice this until now when my theme has also been upgraded. I went through and corrected the last 4 months worth posts that had those offending dashes. I really don’t want to bother finding out whether it’s WP 2.2 or my theme or possibly both. It’s easier just to correct the titles. Go figure.

  6. becky says:

    HI again Kirk, sorry I have not been in touch for a while. I seem to have fallen out with my blog and not read many others.
    Hopefully I can claw my way back again :)

  7. Kirk M says:

    Hi Becky,
    That can happen easily enough. So claw, lady, claw. I would miss you if you weren’t there. :)

Leave a Reply