Browser Add-ons, Flock, Mozilla Firefox, Performancing, ScribeFire, Software

ScribeFire (previously Performancing for Firefox) Updated

ScribeFire logo Version 1.4 of Performancing for Firefox has been released, and in the process, it has been rebranded as ScribeFire. The homepage has moved as well, from Performancing.com to ScribeFire.com.

Besides the name change, this release includes the following changes:

  • Support for Blogger blogs has been improved (now you can even post with ampersands!)
  • We’ve added support for the new WordPress API. What does this mean? If you have a WordPress blog that supports the new API (currently any blog at wordpress.com), you will be able to add, edit, and delete pages directly from ScribeFire, as well as create new categories. (The API will be included in the next major WordPress release, for all non-wordpress.com blogs.)
  • General bug fixes and code optimization.

I’m new to this project, having been asked to pick up where the previous developer left off, so I’m not completely up-to-speed on what the most-requested fixes and features are. So in the spirit of catching me up, feel free to comment below with any feedback until the new ScribeFire.com site is up and running.

You can download ScribeFire from the Mozilla Addons preview site.

Standard

16 thoughts on “ScribeFire (previously Performancing for Firefox) Updated

  1. xaueious says:

    well first of all, the scribefire website still points to the old performancing link on mozilla addons

    I personally use the new blogger. However, Scribefire does not detect the categories I have in blogger.

  2. Found your blog and consequently, much to my delight, the update to the old PFF which I’ve been using since day one, strictly by accident. I was getting frustrated with Performancing’s lack of info since the announcement of Scribefire so I once again Googled around on suspicion that Performancing wasn’t keeping up with events. It’s been the greatest pinch hit blog editor around and I’m glad you picked up on it’s development. Good deal for everybody.

    I worked a bit with Jed Brown as one of the beta testers of the previous 2 versions and had suggestions for the next (1.4) versions all of which still reside in my Performancing account. I suppose I’ll dig them up soon and remind myself what they were. :-)

    One thing though I had previously mentioned, the new “Upolad Via API” option for the image uploader that was included in version 1.3.5 is not available when the editor is opened in a tab. Only when opened in the browser or in a window and I see the new Scribefire has the same problem. Just info here.

    Lastly, I’m a bit puzzled why your release hasn’t been mentioned at Performancing at all. At least I can’t find anything about it. Is Scribefire completely disassociated with the Performancing group or did they just drop the ball again? I can say that because I’m still a (rather silent) member.

    I, for one, thank you for your effort.

  3. @Will: I believe that may be a problem with Blogger rather than with compatibility problems with FF2. I ran both PFF version 1.3.5 since the early betas of FF2 and now ScribeFire version 1.4 in the latest FF2 update. If your using Blogger beta (is it still in beta? I gave up on the new Blogger after encountering too many problems), ScibeFire is probably going to have problems. I know that Jed Brown (the original author of PFF) was working to get PFF fully compatible with Blogger but I don’t know how far that got.

    Other stand alone type editors also have problems with the new Blogger including WLW.

    Just info here.

  4. I just installed Scribefireand i’m kinda sad to say that Scribefire1.4 carries on the same BUG that PFF 1.3.5 had.

    PFF 1.3.5 and Scribefire 1.4 both cannot recognize special characters in the password field during the account setup. By special characters i mean the characters above the number keys from 1 to 0. ANd since i have special characters in my password,,i cannot use Scribefire just as i couldn’t use PFF 1.3.5 unless i change my google password(i use the new blogger). I pointed this out to Jed Brown and thought it’ll be fixed in the new version,but alas, it seems Jed Brown is no longer on the project.

    Kindly fix this bug ASAP.

  5. Indeed this is a must-have extension for Firefox users with blogs.

    But, i’ve some problems with ScribeFire.
    First of all, i can’t edt the properties of an image. Like, if i want the image to float, i manually have to enter style=”float: left;” in the code section. And finding some line in the code section is rather hard.It’ld be good if i select to change to code section, scribefire should automatically go to the line i pointed at wysiwyg section. Also, the property vanishes if you accidentally forgot and move the image to some else place on your post.

    And there’s this, that i can’t choose h1, h2, h3 and kinda tags in my posts. Do i have to use and all the time?

    Also, i’m using Which is a pain in the ass if you try doing that in ScribeFire.

    Ah, and i can’t add title tags to links or images, no matter what. Unless i manually edit the code.

    I don’t know, your plugin is really good in someways, but needs to be better in other ways.

    Can you, somehow, add some of these options? And if not, can you tell me why?

  6. Indeed this is a must-have extension for Firefox users with blogs.

    But, i’ve some problems with ScribeFire.
    First of all, i can’t edt the properties of an image. Like, if i want the image to float, i manually have to enter style=”float: left;” in the code section. And finding some line in the code section is rather hard.It’ld be good if i select to change to code section, scribefire should automatically go to the line i pointed at wysiwyg section. Also, the property vanishes if you accidentally forgot and move the image to some else place on your post.

    And there’s this, that i can’t choose h1, h2, h3 and kinda tags in my posts. Do i have to use and all the time?

    Also, i’m using a name=”” kinda inner page links. Which is a pain in the ass if you try doing that in ScribeFire.

    Ah, and i can’t add title tags to links or images, no matter what. Unless i manually edit the code.

    I don’t know, your plugin is really good in someways, but needs to be better in other ways.

    Can you, somehow, add some of these options? And if not, can you tell me why?

    (Note: I’ve re-posted my comment due to some technical errors of wordpress! The one above can and must be removed. ;) )

  7. I really like the ease of posting the plugin supplies, as well as the del.icio.us integration. Since I’m on blogger, the two problems I have are category tags and image upload. I’m not sure how or if either is possible at the moment. Thanks for the work and looking forward to future updates.

  8. You can’t use & (ampersand) in passwords, it says wrong password.

    Ive written a comment earlier but it was flagged as spam. I hope this gets through your over-zealous filters.

  9. On your catch up request:

    It’s been awhile since the last version on PFF so I won’t be able to be specific (sorry ’bout that) but being involved with the early development (testing) and reading the associated forum at Performancing, one of the biggest complaints about PFF was the html code it generated. It tended to break blogging posts in a minor to moderate way when it came to the posts text formatting and I have found the same thing happening with the new Scribefire. No fault to you of course. I know you’ve kept most of the original code of the extension intact.

    When posting to my WordPress blog (WP install, not “.com”) as a draft from Scribefire and then putting the finishing touches from the WP editor (tinymce) I find that I have to reformat the entire post especially re-spacing and re-connecting lines of text so that they extend the entire length of the post “container”. In fact I stopped posting directly with ScribeFire just for that reason and went to posting drafts instead.

    I’m not intimately familiar with html so may I recommend you do some tests posts to a WordPress blog and see for yourself. I distinctly remember the PFF generated html to be the chief complaint on the old Performancing forum. Unfortunately that forum is long gone. I contacted David Krugg of Performancing to see if that old forum data was still around somewhere and he said he’d check into it but no word back yet.

    Glad your working on this extension for sure. I’d be somewhat lost without it.

  10. I can’t seem to get the scribefire to even register with my wordpress account.
    I keep getting an api at the url doesn’t exsist and I haven’t a clue… I allowed it to manually set it and it just errors.

  11. bernd_fh says:

    Hi Christopher,
    good to hear that development continues. I have the habit of trying to accommodate all computer works in my browser, with FireFox Add-Ons, WP/SquirrelMail/Calendar, etc. on XAMPP.
    So I’m using ScribeFire also for quick note taking. While initially I found once the file containing all my notes I could not replicate it later.
    Can you pls. tell me name and location of the “Notes” file?
    Thanks

  12. Steve Cuss says:

    Hi,

    I’m definitely a novice at blogging, but I have created a blogger account and blog (cusswords.blogspot.com) and I downloaded the scribefire extension, but I can’t find scribefire anywhere on my browser. Where is it and how do I use it to post to my blog account?

    thanks

Leave a Reply

Your email address will not be published.