The next version of ScribeFire for Google Chrome and Safari has been released; the equivalent version of ScribeFire Next is also available.

What’s new in this build?

• “Blog This” option in the context menu (Firefox and Safari only) transfers the currently selected text, link, or image into the editor for easy blogging.
• Tag autocompletion. Any tags you’ve used in your last 20-30 posts will be used for autocomplete.

  

• Custom Fields (Wordpress only).  Custom fields have been fully implemented, complete with autocomplete for field keys.

  

• Better Drupal and Movable Type support. Category selection works now, and publishing to a Movable Type blog has been cleaned up and more fully tested.
• A bug causing linebreaks to be lost has been fixed.
• If you’re running a Firefox 4.0 beta and you open ScribeFire in a tab, that tab will be an App tab.

What’s missing in this build?

• Dynamic layout in Firefox. There were some major bugs in it, and I didn’t want to delay this release just for that one feature.  It will be back (and in all browsers) as soon as it’s working properly.

Google Chrome users, download ScribeFire 1.2.0.0 for Google Chrome here.

Safari users, download ScribeFire 1.2.0.0 for Safari here.

Firefox users, you can download ScribeFire Next 1.2.0.0 for Firefox here.

I’ve just uploaded version 1.1.0.0 of ScribeFire for Chrome and Safari, the first major update to this distribution of ScribeFire since the initial release two months ago.

What’s new?

• The editor is resizable.
• You can customize your post slugs (on supported blogs).
• You can set posts as private (on supported blogs).
• The editor is now powered by TinyMCE, the most usable visual editor out there. (Wordpress also uses TinyMCE.)

• You can add multiple authors for a single blog.
• You can add post breaks in Wordpress.
• You can make the editor full-screen.

Lots of bugs have been fixed as well. If you’re already using ScribeFire in Chrome or Safari, it should theoretically update automatically, but if it doesn’t or if you just can’t wait, you can install ScribeFire 1.1.0.0 for Google Chrome here or install ScribeFire 1.1.0.0 for Safari here.

Today, Apple released Safari 5, the first version of their Web browser to really support browser extensions.

Tonight, we’re releasing ScribeFire for Safari. It’s based on the same code as ScribeFire for Chrome, and it uses the same simple interface. (Thank you Apple for building an extension-building environment simple enough that ScribeFire could be ported in under 90 minutes.)

If you’ve installed Safari 5 and enabled extensions, click here to download ScribeFire for Safari, and then open the file on your computer once it has finished downloading.

ScribeFire is now officially available for Google Chrome. Click here to visit the Google Chrome extensions gallery and install it.

The first beta version of ScribeFire for Chrome is now available for testing. If you are running Google Chrome, you can install it by clicking on the scribefire-0.1.2.0.crx link here. (If you already installed the second alpha, it will auto-update to this release. If you installed the first alpha, you will still have to install this version manually.)

Changes in this update include:

• Insert Image button in the editor
• Cleaned up code that is generated by inserting images or linsk
• Allowing manual blog configurations if ScribeFire can’t auto-configure your blog.
• Quote button
• Xanga support
• Support for scheduling posts

If you have any problems with this version, report a bug by filling out this form at the ScribeFire for Google Chrome project website. To request a feature for a future version, fill out this feature request form.

The second alpha version of ScribeFire for Chrome is now available for testing. If you are running Google Chrome, you can install it by clicking on the scribefire-0.1.1.0.crx link here. (If you already installed the first alpha, it won’t auto-update to this version because I forgot to make it do that. Sorry. This version will auto-update to all future updates.)

Changes in this update include:

• Automatic updates
• New WYSIWYG editor
• Support for Posterous
• Support for LiveJournal
• The editor’s state is now persisted even if you close ScribeFire and reopen it
• Added a button to reset the entire editor to a blank state
• Fixed bug that would reset Wordpress slugs when editing a post
• Fixed bug that caused linebreaks to be ignored when posting to Wordpress

If you have any problems with this version, report a bug by filling out this form at the ScribeFire for Google Chrome project website. To request a feature for a future version, fill out this feature request form.

The very first alpha version of ScribeFire for Google Chrome is now available for testing.  If you are running Google Chrome and would like to test this bleeding-edge version of ScribeFire, you can install it by clicking on the scribefire-0.1.0.0.crx link here.

After you install ScribeFire for Chrome, you'll see a ScribeFire icon in your toolbar. When clicked, that icon will open a new tab that contains the ScribeFire editor.  That editor will look like this:

I've tried to keep the interface so simple that even a caveman could use it.  If you can't use it without me explaining it in detail, then I haven't done my job properly.

Here is a list of features that are expected to work in this first alpha:

• Adding blogs from Wordpress, Blogger, TypePad, Windows Live Spaces, Tumblr, or any blog that explicitly supports the MetaWeblog or MovableType APIs. You should be able to remove these blogs as well, once they have been added.
• Creating new posts for any of the above.
• Editing existing posts for any of the above.
• Saving a post as a draft.
• Tagging and categorizing posts.
• Deleting posts.
• WYSIWYG editor
• HTML Editor (click the "Source" button in the editor's toolbar)

If you have problems in any of these areas, report a bug by filling out this form at the ScribeFire for Google Chrome project website.  To request a feature for a future version, fill out this feature request form.

Development has begun on ScribeFire for Google Chrome. Watch this space for updates and links for alpha and beta testers.

We’re aware that uploading images to Blogger blogs has been broken since late Thursday night. We’re working on a fix and hope to have it up and running as soon as possible.

Some of you may have noticed that after you report a bug with ScribeFire, it can take quite a while before you get a response. I admit that I’ve been a little lax in replying to bugs that don’t seem to apply to a majority of users, but today I’ve gone through the bug list and given a response to every bug that I don’t have enough information on to begin fixing it.

From now on, I’m making a renewed commitment to addressing bug reports as quickly as possible. In order to do this though, I’m going to need your help:

• If you have a quick ScribeFire question or simple bug, you can ping me on Twitter; I’m @cfinke. This method of communication will result in the fastest responses from me.

• For more complex problems, fill out a bug report here. Include as much information as possible, especially the kind of blog you have and the URL of the blog.

• To request a new feature, fill out the same bug report form, but ignore the questions like “What is the problem?” and just tell me what new feature you want.

• If you have a bug that you know will require some confidential information, you can e-mail me directly at chris@scribefire.com. Only do this if there is information in your bug report that you don’t want public.

Thanks for your cooperation; just remember: we’re all in this together.