Toluu

ScribeFire: Fire up your blogging

Scribefire: Fire up your blogging

ScribeFire 1.2.0.0 Available for Chrome, Safari, and FirefoxJuly 26

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 r

Introducing ScribeFire NextJuly 18

The last few months have seen great strides in ScribeFire for Chrome and ScribeFire for Safari, both of which are based upon a single codebase that came from rewriting the main portion of ScribeFire for Firefox. However, ScribeFire for Firefox (a.k.a. ScribeFire Classic®) is still using the old code, making it difficult to fix bugs and get updates out quickly and easily.

In order to allow Firefox users to benefit from the rewritten code being used in Chrome and Safari, I’m introducing a new version of ScribeFire for Firefox, and I’m calling it ScribeFire Next. (As in, “This is where ScribeFire is going Next.”) ScribeFire Next uses the same codebase as ScribeFire for Chrome and Safari, but it’s integrated into Firefox in the same way as ScribeFire Classic®.

There are a few differences between ScribeFire for Chrome and ScribeFire Next:

• ScribeFire Next supports image uploads.

  Neither Chrome nor Safari have the necessary features that allow developers to integrate file uploads into extensions, but Firefox has had those features for ages.

ScribeFire for Chrome and Safari 1.1.0.0 ReleasedJuly 13

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.

ScribeFire and Safari, Sitting in a TreeJune 7

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 Officially Available for Google ChromeMay 17

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