We’ve released ScribeFire 1.4.1 on Mozilla Addons. Here’s the changelog from version 1.4.0.1:
- Navbar is now collapsed by default
- Rotated nav bar toggle to show direction of flyout
- Shrunk sidebar toggle to match navbar toggle
- Restyled publish button to be more consistent
- Moved navbar and sidebar toggles into the top row the editor to save space
- Categories have been relabeled as tags
- Added confirmation to post deletion
- Blog list now uses radio buttons
- Added link to each blog in blog list
- Removed “View this blog” link from bottom of editor
- Put blogs, tags in groupboxes
- Moved “add/edit blog” button into groupbox
- Moved “add tag” button into groupbox
- Fixed bug where all spaces were being encoded as
- Added Strong, Em buttons to editor
- Fixed blockquote button
- Added Dutch translation
These are mostly interface changes; in the next few versions, we’ll be looking more closely at fixing bugs and adding the most oft-requested features.
July 17th, 2007 at 6:45 pm
[...] 1.4.1 has been released. See the ScribeFire blog for details on what changes have been made, or download it from Mozilla [...]
July 17th, 2007 at 6:59 pm
I am getting a download error from the Mozilla site when I attempt to update.
July 17th, 2007 at 7:01 pm
Try again in a few minutes; this happens sometimes shortly after an extension is updated.
July 17th, 2007 at 7:30 pm
[...] new release of the Firefox blogging add-on, ScribeFire 1.4.1, is on Mozilla Addons. It looks much more polished. The change log is at the blog article [...]
July 17th, 2007 at 8:10 pm
Excellent work… look forward to the additional updates and an interactive forum.
(I may have also experienced a hiccup on installation. I had the IE browser window open and can’t recall if I also had FF open or not. I did see an installation failed message.)
However I quickly opened FF went to my addons screen in FF and went to TOOLS – ADD-ON and ran FIND UPDATES. The update popped up and it loaded when clicked and asked for a restart with no issue. Sorry I could not validate the error condition more exactly. It was no big deal however. The GUI looks good!!
ZZ
July 17th, 2007 at 8:51 pm
[...] ScribeFire PreviousTags: Download, Extension, FireFoxCategory: Wordpress, Open Source, Blogging, [...]
July 17th, 2007 at 9:11 pm
Guys… Did you intentionally remove the close window icon in the upper right hand corner of the ScribeFire window? IMHO not a good idea as it is an almost universal place to look to close a window during the past 20 years
I am sure it was there in the last revision or perhaps I was imagining things. It appears to close the window you have to click once again on the tool bar icon? Seems a bit awkward to me. Just my opinion.
July 17th, 2007 at 9:14 pm
Review: New Release of ScribeFire
ScribeFire 1.4.1 by Christopher Finke was released today by scribefire.com (previously Performancing for Firefox). It’s a great plug in for Firefox users that actively blog. Several GUI enhancements were made, mostly cosmetic, to the previous revisio…
July 17th, 2007 at 10:41 pm
When will there be Firefox 3 support?
July 18th, 2007 at 1:02 am
[...] Firefox下最好的åšå®¢ç¼–辑工具ScribeFireå‘布了最新的1.4.1版，点击这里下载或更新 [...]
July 18th, 2007 at 5:52 am
I agree with zzb above – I find it awkward that the close window button has been removed. Is there a rationale for that?
I also miss my old, bold publish button, as well as the idea that text labeling a button should be in the center of the button.
Is it also possible to get blog entries marked in ma.gnolia and StumbleUpon the way the del.icio.us thingy works?
I use ScribeFire way too much, sorry for all the comments and complaints. It’s like my one blogging toy.
July 18th, 2007 at 12:31 pm
I agree to zzb and ashok. Removing the close button was a bad idea. I’ll downgrade to 1.3.5 till the button’s back.
July 18th, 2007 at 4:33 pm
The changes look good so far…I never use the close button, so that doesn’t affect me
(that’s what F8 is for, BTW…opens and closes SF).
On the other hand in the coming-soon post you talked about the publish-later option…but I can’t find it anywhere! Did it make it in? If so…where is it?
Thanks for all the good work
July 18th, 2007 at 6:57 pm
Vox — Thanks for the F8 tip!
I am sure the tweaks next week will be worth it. Small red close box icon similar to the close tab in FF should look fine in the upper right corner should match with most themes I would imagine. Pretty standard. Maybe a check box under General that if checked renders the close box present or not (default present) and perhaps some other cosmetic features might be toggled as well?? The user could config look and feel a bit more but I wouldn’t go overboard. I don’t know how difficult the programming challenge would be.
July 18th, 2007 at 10:05 pm
You welcome
As for the cosmetic stuff…in theory SF is theamable, so…that should take care of that. In my personal case, I don’t much care about its looks, as long as I can leave it as is so it matches my FF theme.
On the other hand, that publish-later thing…that I do want
July 18th, 2007 at 10:55 pm
One of my favourite firefox extensions – I couldn’t live without it! Agree with above points for the update:
1. close button was good.
2. Highlighted publish button is sorely missed.
Also
3. Losing the “view this blog” link next to published sucks – if I haven’t got the “blogs” window open then it’s too many clicks away. It was nice having this on hand to quickly double check that the post looked okay live.
4. In the last version, the publish button also told you which blog it was publishing to – this version seems to have lost that it just says “publish” instead of “publish to blogname x”. Was good if you have multiple blogs and was a reminder not to upload the post to the wrong blog (not good if you accidentally post a personal post to a work blog).
Looking forward to the tweaks hopefully these easily ignored features will return. Other than that, thanks heaps for continuing to develop such a great app!
July 18th, 2007 at 10:56 pm
Yes publish later would make scribefire close to perfect.
July 18th, 2007 at 11:04 pm
I don’t mean to be “that guy,” but when are you planning on fixing it so that your awesome little plugin actually works for everybody using Wordpress? Again on this version, it refuses to log in.
July 18th, 2007 at 11:31 pm
Oh! Yes, Kitty is right about her point 4…the “Publish to ” was awesome…can we get that back, please? I just published my first post from the new version and…I had to go check to make sure I was publishing to the right blog.
Maybe activate it if you have more than one blog configured and just keep “Publish” when it’s only one blog configured…that’d give us the best of both worlds
July 18th, 2007 at 11:38 pm
Saw that you are putting the close button back. Yeah! And am sooooo happy the space thing has been resolved, as that was a pain.
One other thing, I don’t mind that the “view this blog” button has disappeared (although I miss it and used it constantly), but clicking on the blog name opens a completely new Firefox window for me instead of opening in a new tab as the “view this blog” did, which sucks completely, and you can’t even right click to open in new tab. Makes it annoying to use, now, and I loved to view my blog after each post (I know, I’m weird). Can this be changed so that it will open in a new tab in the same window? or bring back the “view this blog” button?
July 19th, 2007 at 5:39 am
Looks nice but I too wondered what happened to the little close window ‘x’. Aside from that, SF has worked well since the last version with my WordPress blog. Good job!
July 19th, 2007 at 2:54 pm
NOOOOOO. You’ve broken a feature that I absolutely needed. Previous versions I could hover over the blog name and a hover help would tell me what site it was for. That is gone. I now have a list of blogs that all read gfox: blog.
If you could fix that, put back the old behaviour, or allow me to enter an alias for a blog that would be ever so helpful. Now I need to find a way to revert to the previous version.
Greg
July 20th, 2007 at 2:47 am
I have to say that my user experience hasn’t been enhanced by these (mostly cosmetic) changes. Why has the ‘view this blog’ button been removed? And, like Angela above, why does the blog open in a new window? And why remove the blog indicator on the publish button? None of these things has enhanced the experience but rather the opposite. The radio buttons have added nothing as far as I can tell, except to make the interface more ugly. Sorry to be negative but I use SF constantly (I’ve posted about 2,500 entries with it) and the old version was easier to use and looked better. I hope I can get a copy of the previous version.
July 20th, 2007 at 7:16 am
Clicking on my account in Scribefire takes me to website.net/blog/1. But, there’s no content at that URL. I don’t have blogging turned on for my Drupal website so going to that URL doesn’t make sense. I post via stories, as recommended in Drupal blog recipes.
July 20th, 2007 at 10:56 am
Argggghhhh, I totally don’t understand how to close scribefire now!
What orange bar are you talking about?
This really sucks! I cannot find any way whatsoever to close it!
This is now completely interfering with my non-blogging activities.
I need an immediate fix!
July 20th, 2007 at 10:58 am
I’ve having problems, while the GUI seems to have changed, when I go to the about page is still says I have the 1.3.5 VERSION. Is this hiccup or bug?
July 22nd, 2007 at 2:37 pm
It seems pretty easy to me.
July 23rd, 2007 at 12:21 am
When I click the orange icon all I get is the scribefire page … is this due to scribefire or the most recent FF upgrade (2.0.0.5)? Now I can only use it in a window or tab.
July 23rd, 2007 at 12:40 am
It’s working now-had to restart FF.
July 23rd, 2007 at 7:08 am
how can you get it to not remember the blog account password. I don’t like the idea that it stays logged into the blog editor?
July 23rd, 2007 at 2:06 pm
I really wish you’d stop tinkering with this plugin, every version is worse than the last. Right now, the list of blogs looks scruffy, the close button is missing and I can’t post to my self-hosted WP blog. Time to take another look at Deepest Sender…
July 24th, 2007 at 8:39 am
Is it intentional that the “about” page still shows 1.3.5 as the version number?
Aside from that, this seems like an excellent little tool. My one gripe would be the “powered by Scribefire’ link at the bottom of each posting (or at least each posting I’ve made so far). I understand that you want to promote Scribefire, but IMHO it looks unprofessional on a business blog. Is it intended that there would be (or already is) a commercial version without it?
July 24th, 2007 at 2:53 pm
For me the “quote” button now trashes every entry. Everything I cut and paste, then format has to be reformatted. I’m likely using some other tool until the next version. This release doubled the work it takes for me to post and is just unusable.
July 25th, 2007 at 4:18 pm
“The J Train” wins a gold star for seeing right through us. Posting to multiple blogs is in our roadmap, and moving to radio buttons is the stepping stone between a list and checkboxes.
July 27th, 2007 at 1:50 pm
“Strong” and “em” tags are finally on the rich text editor’s toolbar. Still, few more useful are missing. To add h1 through h5, p, tags download this ( http://laffers.net/downloads/better-scribefire.zip ), and copy the files packed therein over those installed in your Firefox profile folder (on Windows it is something similar to
C:Documents and Settings{insert your username}Application DataMozillaFirefoxProfileskvbo025t.defaultextensions{F807FACD-E46A-4793-B345-D58CB177673C}chromecontent
)
Note: I made it relatively easy to add whatever tag you wish. Take a look at the code (performancingMidas.doApplyTag(tag) function is the key) and see how it is done.
Cheers,
Rich
July 28th, 2007 at 4:45 am
[...] Finke und Serendipity klappen könnte. Mal sehen.Natürlich gibt es auch ein extra Blog Blog, bei dem die User ihre Erfahrungen dazu austauschen können. Ich für meinen Fall kann nur [...]
July 28th, 2007 at 11:44 am
If it ain’t broke don’t fix it. How can we remove 1.41 and go back to the earlier version that worked fine.
August 1st, 2007 at 4:18 am
To remove the “powered by Scribefire” from you posts just edit the “editor.js” file and comment out line 835. i.e. change the line
performancingUI.appendText( theText );
to
//performancingUI.appendText( theText );
August 1st, 2007 at 10:49 am
Edit a file? uhm…wouldn’t it be easier to de-select the option “Automatically add Powered by Scribfire” in the Options? At least I’d hope so.
August 7th, 2007 at 2:16 pm
Kudos for the great work… I just wanted to drop a note to tell you that, when category name includes some punctuation (a comma in my case), Scribe gets confused and gets only up to the mark. A regexp problem maybe?
Thanks…
February 7th, 2008 at 6:50 am
scribefire is a good add on but just for mozilla?
April 3rd, 2008 at 6:55 am
[...] writing a post about this entry http://www.scribefire.com/2007/07/17/scribefire-141-released/ Stay [...]