Blogging Robots

New beta version of BlogJet 2.5

February 3, 2010 by Dmitry

The development of BlogJet 2.5 is progressing nicely, and we’re happy to announce a new beta version.

blogjet-live-spelling.png

What’s new

  • Live Spelling, and a lot of spelling options (including auto correction)

  • Fixed not remembering window position and size.

  • Fixed overwriting custom HTML/JavaScript settings for BlogJetThis! when installing.

  • Fixed treating punctuation as spelling errors.

Special thanks to Jack Vinson and other testers for reporting many of these bugs.

Known Issues

We’ll address the following issues in one of the next beta versions:

  • Embedded Flash video clips (including YouTube) appear as black boxes (affects only appearance in editor, posting works well).

  • Windows Vista/7 only: you need to launch BlogJet as administrator from Windows Explorer to add words to dictionary.

Download BlogJet 2.5.0.4 Beta (4.3 MB)

Please report any bugs you encounter in our beta forum.

BlogJet 2.5 Public Beta

December 30, 2009 by Dmitry

We’re happy to announce a holiday present for you — a public beta of BlogJet 2.5!

What’s New

  • Full Unicode support.
  • New spell checker (you can download dictionaries here).
  • Clean theme that looks awesome in Vista and Windows 7.

Download BlogJet 2.5 Beta (4.3 MB)

Full Unicode support is a big deal. You can write posts in any language and even mix languages:

Unicode in BlogJet

Development and Next Releases

Now that we released 2.5 beta, the transition to a new code base (with most core parts completely rewritten) and a new development environment is done, so we’re ready to continuously improve BlogJet and release new versions faster.

BlogJet Beta Forum

We’re starting to be more open about BlogJet development, and replacing the closed beta forum with an open one. Please join us in BlogJet Beta Forum. You can report bugs in beta versions there.

Happy New Year! Enjoy the new BlogJet!

Updated BlogJetThis! extension for Firefox 3.5

November 30, 2009 by Dmitry

One of the updates to Firefox 3.5 broke BlogJetThis! extension: it worked only once, and after that Firefox showed an error (NS_ERROR_ALREADY_INITIALIZED).

We have updated the extension. You can download it from BlogJetThis! support page.

Thanks to everyone who reported the issue!

BlogJet 2.0.1.4 Released

August 31, 2009 by Dmitry

We are happy to announce a small bug-fix release of BlogJet. It fixes connection issues with some Blogger blogs, and includes an updated extension for Firefox 3.x.

We’d like to apologize for not releasing the fix for Blogger issue earlier. We were transitioning our code base to an updated development environment and rewriting core parts of the program, thus changes on Blogger’s servers caught us in an unfortunate time.

Enjoy the new build, and expect more to come in the not-so-distant future!

You can download the new version from http://www.codingrobots.com/blogjet/download/. There’s no need to update if you didn’t have issues described above.

Mémoires is compatible with Snow Leopard

August 26, 2009 by Dmitry

Mac OS X 10.6 “Snow Leopard” is coming on Friday, August 28. I’m happy to announce that Mémoires is fully compatible with it, no upgrades required.

(Of course, if you encounter any bugs that our testing missed, please let us know.)

On Anchored Selections in Windows, Gnome, and Mac OS X

April 28, 2009 by Dmitry

Pierre Igot wrote a blog post “Shrinking and expanding selections in Mac OS X(via Daring Fireball), in the first part of which he explains how text selection works on Mac OS X, and complains that this behavior is wrong. I disagree.

Let me explain. On Windows and Gnome, when you’re selecting text with mouse, the anchor is being placed on the final point of your selection (and it’s displayed with a blinking indicator in some applications like Notepad). If you select text from left to right, the anchor appears at the end of your selection:

Windows: anchor at the end

If you go from right to left, the anchor is at the beginning of it:

Windows: anchor at the beginning

Pierre writes:

What if I overshot by one character or two and actually only wanted to select the first two words? To me, since the selection with the mouse was made from left to right, intuitively I should be able to shrink the selection by one or two characters by pressing shift-Left a couple of times on my keyboard.

This seems logical: if you go left to right, you’ll probably miss a character of two, so placing anchor to the end of your selection is the right way. But this logic is flawed. It’s no harder to miss a character when you begin selecting text, than to miss it when you finish. Actually, there’s no way to select missing characters at the beginning at all, apart from starting your selection from scratch. There’s also a problem with double-clicking the word. Where should be the anchor placed in this case? Windows places it at the end of the word, while Gnome places it at the beginning.

Cocoa text controls behave differently. When you select text with mouse, the anchor is undefined. When you switch to keyboard, you control the anchor point: if you start by pressing Shift+Right, the anchor is being placed at the end of your selection, but with Shift+Left it’s being placed at the beginning. This way you can easily select missing characters in any part of your selection. Also, without anchor, you can continue growing your selection both ways.

Notice that I didn’t say that Mac OS X behave differently, just Cocoa. Carbon handle this the third way (the anchor is always where you click), but Apple is getting rid of it. That’s why Finder has anchored text selection with mouse. Good thing there are rumors that it’s being rewritten in Cocoa for Snow Leopard.

Yes, there’s inconsistency between text selection and list selection, but I have no explanation for this :)

Update: Pierre published a follow-up.

Good news

March 7, 2009 by Dmitry

Just a short post to let you know what’s going on here at Coding Robots.

First off, January 2009 was the best month ever for the company since 2002. We’re looking forward to investing our time and money to bring you new versions of our products and some more fresh software.

BlogJet users would be happy to know that there’s a new version in development (as usual, we don’t disclose release dates, so stay tuned).

Mémoires 2.0 has been released recently, and there is an update in the works, so keep your feature requests and bug reports coming.

Finally, we’re working on an exciting new (secret) project that will revolutionize the way you                and               . We hope it will see the light of day this year.

Thank you for your support! Stay tuned.

Leaked email from CEO

January 31, 2009 by Dmitry

From: Dmitry Chestnykh
To: All Staff
Subject: SOME BUTTONS TO BE DISABLED

Dear staff,

As you may have heard, bright minds over at Nielsen removed “Reply to All” button to eliminate bureaucracy and inefficiency.

Today Coding Robots Executive Council held an event called ¡ACT IMMEDIÄTELY!, and we developed a plan (inspired by can-doers at Nielsen) to further improve our productivity.

We developed four Mail toolbar configurations for different departments.

Support

Our technical support staff can have only two buttons: Get Mail and Reply. Obviously, they don’t need New Message and other non-productive buttons.

Sales and Marketing

Sales and marketing can have four buttons: Get Mail, New Message, Reply to All, Add Address. We are aiming for the best exposure, that’s why they don’t have Reply button, and have Reply to All instead. They can’t have Forward button, because everyone out there is tired of Internet memes.

Developers

Developers can have three buttons: Get Mail, Bounce, Junk. They never use Reply and New Message anyway.

Executives

Finally, we, executives, decided to place stricter constraints on ourselves. Executives are allowed to have only one button: Take All Accounts Offline.

This is one of the many changes being implemented as a result of the ¡ACT IMMEDIÄTELY! initiative. In my next email I’ll talk about removing unnecessary buttons from your keyboards to further spread the productivity virus!

Best,
Dmitry Chestnykh
Chief Executive Officer

Check out: