Archive for June, 2011

We are happy to announce the awesome new release of BlogJet 2.6.1, our blog editor for Windows.

What’s New

• Live Preview and Markdown support.

• Shortcut for Post as Draft (Ctrl+Alt+Enter).

• Asking to save draft after publishing or posting as draft problem fixed.

More about preview and Markdown

You can now preview your post while writing. Because preview window supports Markdown filter, you can easily write Markdown-formatted text.

Each blog account has a preview template file, so you can edit preview file to apply different styles to different blogs. Preview template is stored along with accounts file (not Program Files/BlogJet/Data because it need admin account to write it on Windows Vista and 7). Click “Edit Template” button in Preview to open folder with template file.

This preview file is also used in Recent Posts preview.

Note about Markdown preview. When you select Markdown filter, Normal view (WYSIWYG Editor) is disabled because switching between Code editor (Markdown text) and Normal editor would have corrupted your Markdown text. You can set default preview filter option at Manage Accounts (F5) window.

Please note that Markdown-formatted text is not converted to HTML by BlogJet when posting, it requires you to turn on Markdown filter in your blog server. It’s easily done in WordPress and Movable Type — please refer to your blog server software documentation.

Download

As usual, you can download the new version of BlogJet from its product page.

We are happy to announce the release of BlogJet 2.6!

What’s New

• Background networking for posts refresh, posts delete, categories refresh, creating and deleting categories.

• Recent Posts now has slide mode with content preview. You can switch back to column mode (multi selection is only available at column mode).

Get It

As usual, you can download the new version from BlogJet product page on our website.

Hi, my name is Kim Young Hoo and as you may know, I work with Dmitry at Coding Robots, mostly on BlogJet and iOS applications.

We’ve just released a new small update for BlogJet, version 2.5.3. It includes a fix for a fundamental problem with post status. Let me explain what the problems was and what the fix does.

BlogJet have three statuses for posts. In older versions, you could see it at the right-hand part of the status bar. In the new version it has been moved to the properties pane under the “Status” label.

Statuses:

• New Post. As you can guess, it means a new post. When you click “Publish” if post status was ‘New Post’, BlogJet makes a request request to your blog service to create a new post. Easy.

• Editing. Editing means that the post has been already published (as a draft or not) to blog. So BlogJet request to update existing content with “Editing” status.

• Draft. When you save your post to a draft file or open the existing draft file, the post status is “Draft”. For such posts, does BlogJet makes a request to create new post or update existing post? Try it. Make a sample post. Publish it. Save it as draft file. Exit BlogJet. Launch BlogJet and open a saved draft file (now “Draft” mode). Publish it. Update or new?

The answer is, new post. Because BlogJet doesn’t save published status in the draft file, it’s always recognized as a new post. Draft file feature exists to save drafts when writing (before publishing) or for content backup, so it isn’t right to manage local copies of published posts.

I’m sure there are some people who don’t like this “always new post” thing for draft. But soon BlogJet will have “save draft” or “auto save” to local database feature, so I don’t want to fight with the above problem for now.

There is another status: for WordPress blogs we have “Page” or “Post”. It coexists with above three statuses. New Post or Page, Editing Post or Page, so on.

Nothing special. Simple. New Post, Editing, and Draft. For WordPress, page or post. Simple.

The problem appears after you publish a post to a certain blog (let’s call it “A blog”). If you switch the blog to “blog B”, what the status of this post will be?

In older version, BlogJet didn’t do anything for this “change blog after publishing” action. So the post still had “Editing” status. So when you clicked “Publish”, it would try to update the non-existing post (a post published to “A blog”). The result depends on your blog server. You might get an error, or nothing happens, or somehow a new post is created.

In 2.5.3, this problem is fixed. Status will be changed to “New Post” when you change a blog to B and back to “Editing” when you change it to A. Even with selected categories. So BlogJet now manages published states properly.

I know this is a small fix but hope it will reduce confusion.

BlogJet 2.5.3 has been released and is available from the product page.

What’s New

• Status bar removed. Normal/Code view buttons and Pings buttons are in the toolbar.
• Post status, word count, and Page/Post choice have been moved to the properties pane.
• Heading 1-6 button in the toolbar. If there is selected text, it makes it the heading. If there’s no selection, it asks you for the heading text.
• Fix for a post status problem. It needs a longer explanation, so please check the upcoming post to learn more.