We understand that Blogo tries to keep image placement simple, but users shouldn’t have to deal with raw HTML just to get word-wrapping done right. If my image is so tall that it spans multiple paragraphs, and I have it right-aligned, the text in all affected paragraphs should stay to the left of the image. However, when we tested Blogo, we had difficulty with this, as the affected text often jumped below the image, even if the right-alignment was selected.

In regards to a tag-list in a separate window, users with smaller screen resolutions can simply choose not to display the tag-list. However, for blogs with many tags, authors may find it useful to bring such a list up, else they may forget to add a tag. Trying every letter combination just to see which tags we’ve previously used is simply cumbersome. Not to mention, the screen real-estate issue is moot since most authors only need to see this window once, right before publishing their posts. It’s not like this list needs to be up all the time, as it is in ecto.

In regards to the post-date issue, we’ll have to do some more experimentation, because ecto failed in this regard today also, even though it’s been solid for us in the past. Maybe it’s a problem with the latest version of WordPress, and not something specific to Blogo/ecto. If we learn more about it, we’ll be sure to post about it.

Images: We are aware that image placement is limited. This is to keep things simple and limit the possibility for messing up the blog layout by placing the image in the middle of a paragraph, which is a common issue with other editors like Live Writer. If you want to place your image at an arbitrary place in the text, you will have to unfortunately get down to the HTML.

Tags: We designed this to minimize the space needed for tags and categories. A list view or another window with a large tag set would eat up screen real-estate.

Margins: We’ll allow for more customization of the margins set by Blogo in a future version as we expand the options for the HTML output by it. We know that it’s still not perfect, valid XHTML, and we will work until we get it right.

Post date problems: This is the first we’ve heard about this, and scheduled posts were tested. Can you reproduce the problem consistently on your blog?

Formatting: We are aware of the formatting issues when no text is selected. This was an unfortunate side-effect of a workaround we had to do for WebKit’s bad behavior when erasing links. We will be fixing it as soon as possible.