April 29, 2014

Whats new in Version 4.3.1

Filed under: Firefox, Good News Everyone, Google Chrome, Opera, Releases, Safari, ScribeFire -- cmanjoine @ 05:35pm

Version 4.3.1 of ScribeFire for Firefox, Chrome, Opera and Safari is now available. This version includes the following changes:

Bug Fixes

  • Fixed blogger making new posts
  • Re-introduced livejournal.com support
  • Fixed image uploading issues
  • Added browser spell checker
  • Various other UX improvements

Use the links on the right to install or report any issues.

November 3, 2011

ScribeFire 4 is Available

Filed under: Firefox, Good News Everyone, Google Chrome, Opera, Releases, Safari, ScribeFire -- Christopher Finke @ 09:31pm

Version 4 of ScribeFire for Firefox, Chrome, Opera, and Safari is now available. This version includes the following changes:

New Features

  • Using OAuth authorization for WordPress.com blogs
  • Using OAuth authorization for Blogger blogs
  • Added support for “Read more” in LiveJournal blog posts
  • Private posts in Posterous
  • Upload images by copy and paste (Chrome only)

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

Safari users, download ScribeFire 4 for Safari here.

Firefox users, you can download ScribeFire 4 for Firefox here.

Opera users, you can download ScribeFire 4 for Opera here.

September 12, 2011

ScribeFire for Firefox is about to change

Filed under: Announcements, Firefox, ScribeFire, ScribeFire Next -- Christopher Finke @ 09:00am

After more than a year of testing, ScribeFire Next (the version of ScribeFire available for Chrome, Safari, and Opera) will be replacing the old version of ScribeFire on Firefox. I’m giving you a heads-up, because change is hard on us all.

What Changes Will I Notice?

For one, the sidebar will move from the right to the left. Other changes you’ll notice:

  • More frequent updates
  • Faster bug fixes
  • New features, faster

As you might have noticed, they key words here are “frequent” and “fast”: the way that the new version of ScribeFire is built (using HTML5 and other Web standards) allows for much quicker development than the code that the old version of ScribeFire was based on.

Your blogs and notes will transfer automatically, as well as any settings that are supported in the new version. You’ll still be able to use ScribeFire in split-screen mode, its own tab, or its own window.

What happened to [Feature X]?

You might find that New ScribeFire is missing a feature you relied on; not every feature from Old ScribeFire was transferred over. This was done in order to keep the add-on simpler and fast. If this is the case for you, you have a few options:

  • File a bug report to request the feature’s restoration.
  • Downgrade to the previous version of ScribeFire, but be aware that you will not receive updates to fix bugs or compatibility problems with blogs.
  • Bonus option: Try ScribeFire Next early and post a comment below reporting any problems you have with it.

To sum up: don’t panic, stay calm, and we’ll get through this.

September 4, 2011

ScribeFire 1.9 is Available

Filed under: Firefox, Google Chrome, Opera, Releases, Safari, ScribeFire, ScribeFire Next -- Christopher Finke @ 01:01pm

Version 1.9 of ScribeFire for Chrome, Opera, and Safari, and ScribeFire Next for Firefox, is now available. This version includes the following changes:

New Features

  • Added a setting page.
  • Added ability to publish to multiple blogs at once
  • Post templates – save any post as a template for future use.
  • “Blog This” now uses a custom template like it did in Firefox.
  • Added table management features to the editor.
  • Support for Dreamwidth blogs
  • Added ability to specify a default link target
  • Added option for right-to-left text

Bug Fixes

  • When resizing images by manually changing the width or height, the aspect ratio is preserved.

Upcoming Features

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

Safari users, download ScribeFire 1.9 for Safari here.

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

Opera users, you can download ScribeFire 1.9 for Opera here.

July 21, 2011

ScribeFire 1.8 is Available

Filed under: Firefox, Google Chrome, Opera, Releases, Safari, ScribeFire, ScribeFire Next -- Christopher Finke @ 10:06pm

Version 1.8 of ScribeFire for Chrome, Opera, and Safari, and ScribeFire Next for Firefox, is now available. This version includes the following changes:

New Features

  • Added support for Markdown in the code editor
  • Added ability to edit a blog’s username and password without removing and re-adding the blog.
  • Added ability to write and save drafts without setting up any blogs

Bug Fixes

  • Fixed bug causing buttons to be blank
  • Improved support for My.Opera blogs

Upcoming Features

Version 1.9 is expected to have both post templates and auto-saving of post revisions, so if you have an opinion on either of those features, be sure to give your input soon.

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

Safari users, download ScribeFire 1.8 for Safari here.

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

Opera users, you can download ScribeFire 1.8 for Opera here.

June 6, 2011

Contribute test accounts to ScribeFire

Filed under: Announcements, Development, Feedback, ScribeFire -- Christopher Finke @ 03:45pm

I’ve been hard at work the past few weeks automating the way that ScribeFire is tested before a new version comes out. These new automatic tests now allow me to test the major functions of ScribeFire in a few minutes – previously, this would have taken hours manual testing – and already, the tests have uncovered bugs in ScribeFire’s support for Tumblr, Posterous, Blogger, WordPress, and Xanga. (These bugs have been fixed for the next update.)

If you run a blogging service that you want ScribeFire to support (or if you’re a fan of a service for which you want support added), here’s what you can do: create a test account for use by ScribeFire and email the blog URL, username, and password to chris@scribefire.com. (Do not send usernames or passwords for your real accounts.) I’ll add these accounts to the gamut of tests that run before I release a new version of ScribeFire; if any bugs have arisen that affect the way that ScribeFire interacts with those accounts, I’ll be able to fix them before causing you any trouble.

I already have test accounts for the following services: Blogger, WordPress, Tumblr, Posterous, LiveJournal, and Xanga. Accounts for Drupal, Joomla, and MovableType/TypePad are high on my wishlist.

May 14, 2011

ScribeFire Next 1.6 Released

Filed under: Announcements, Firefox, Google Chrome, Opera, Releases, Safari, ScribeFire, ScribeFire Next -- Christopher Finke @ 03:33pm

Version 1.6 of ScribeFire for Chrome, Opera, and Safari, and ScribeFire Next for Firefox, is now available. This version includes the following changes:

New Features

  • Drag-and-drop image uploading in Chrome and Firefox. Just drag and drop one or more images into the editor, and they will upload automatically. (Note: This feature is still a work in progress; please report any bugs you experience with it.)
  • Notes will now import from ScribeFire for Firefox into ScribeFire Next.
  • Ability to insert related images from Zemanta.
  • Import/export feature to help you move your ScribeFire settings between computers.

Bug Fixes

  • Fixed image uploading to WordPress in Firefox
  • Updated Posterous API functions
  • Fixed display of non-ASCII fonts in Firefox.
  • Fixed support for new YouTube embed code
  • Pressing Return in the the “Add a link” dialog now submits the form and closes the dialog.
  • Improved import process of blogs from earlier versions of ScribeFire

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

Safari users, download ScribeFire 1.6 for Safari here.

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

Opera users, you can download ScribeFire 1.6 for Opera here.

February 22, 2011

More Layout Feedback Requested

Filed under: Feedback, ScribeFire, ScribeFire Next -- Christopher Finke @ 05:18pm

This is the current state of the layout for the next update to ScribeFire. In the left-hand column, we have the Blogs dropdown, the Posts dropdown, Categories, and Tags; in the larger right-hand section are the Title, Editor, and Publishing Options. (Click the screenshot for a larger view.)

I think that this arrangement gives the maximum amount of space possible to the editor while still keeping the other portions of the interface easily available.

What do you think? What would you change? What changes do you like?

February 14, 2011

ScribeFire Needs Your Feedback

Filed under: Feedback, ScribeFire, ScribeFire Next -- Christopher Finke @ 05:07pm

I’d like your feedback on the layout of ScribeFire for Chrome (and ScribeFire Next for Firefox). Some users have complained that the current interface takes up too much space, or that it’s too cramped, or that it’s not cramped enough, or that it doesn’t take up enough space. Which of the following would you prefer? (Click each screenshot for a larger view.)

1. The current layout:

2. A bottom toolbar that lets you switch between sections like “Edit,” “Categories,” “Tags,” and “Publish:”

3. A mini-sidebar that moves Categories and Tags into a sidebar next to the editor:

4. A bigger sidebar that moves everything except the post title and editor into a sidebar:

5. Something else. (Explain yourself in the comments.)

Please leave a comment with the number that you’d vote for. Keep in mind that these are just rough approximations; ignore things like the exact colors or spacing between buttons.

November 23, 2010

ScribeFire 3.5.3.2 Un-Released

Filed under: Releases, ScribeFire -- Christopher Finke @ 10:09pm

ScribeFire 3.5.3.2 was released yesterday, but today we had to remove it, as a large number of users reported that it caused their toolbar icons to disappear. ScribeFire 3.5.3.3 has been uploaded to the Mozilla Add-ons site; it is simply a copy of the previous version, 3.5.3.1.

Sorry for the inconvenience; we’re trying to figure out what went wrong, and we’ll have it fixed for the next update.