Comments on: Sage 1.4.12 Released

By: zqwerty

zqwerty — Sat, 20 Oct 2012 15:43:15 +0000

Thanks for fixing

By: Peter Andrews

Peter Andrews — Sat, 13 Oct 2012 02:11:25 +0000

I’m aware, and we should have a fix out soon.

http://code.google.com/p/sage/issues/detail?id=85

By: zqwerty

zqwerty — Sat, 13 Oct 2012 02:05:44 +0000

No longer working correctly in Firefox 17

By: Gero

Gero — Wed, 26 Sep 2012 21:27:07 +0000

Still works great. It would perform much better, if marking all items as read would not put them into history, or alternatively if only those currently being unread were put into history. Current behaviour adversely affects autocomplete, since many items that the user never has actively seen, appear there because of being multiply put into history.

By: ted

ted — Sat, 31 Mar 2012 07:42:14 +0000

how can i tell which version, (release) i have.

By: Jonas

Jonas — Sun, 13 Nov 2011 20:38:08 +0000

Strange, had to reinstall it. Works now, thanks!

By: Peter Andrews

Peter Andrews — Sat, 12 Nov 2011 09:13:47 +0000

The latest release of Sage should be compatible with Firefox 8.

By: Jonas

Jonas — Sat, 12 Nov 2011 09:10:48 +0000

Hi, any news on when a FF8 compatible version will be out?

By: Peter Andrews

Peter Andrews — Wed, 17 Aug 2011 07:34:40 +0000

Sage is now listed as Firefox 6 compatible. Checking for updates should re-enable it.

By: Dave

Dave — Wed, 17 Aug 2011 03:29:00 +0000

It definitely doesn’t work with FF6. Any chance you’ll be making an update soon? Sage is my FAVORITE RSS reader and I really will miss it until there’s an update.

By: John

John — Sun, 14 Aug 2011 20:17:35 +0000

Need a fix for Firefox 6

By: Asthur

Asthur — Thu, 04 Aug 2011 14:29:07 +0000

It works with Aurora build. Version 7.0a2 (2011-08-03)

By: Schimi

Schimi — Wed, 13 Jul 2011 16:47:58 +0000

HI,

don´t worl with Firefox 6 Beta

By: Peter Lairo

Peter Lairo — Sat, 09 Jul 2011 09:20:52 +0000

Do you get the compatibility reports from the “Add-on Compatibility Reporter”[1] add-on?

[1] https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/?src=api

By: pd

pd — Wed, 22 Jun 2011 22:47:47 +0000

Definitely. I was thinking the same. I think version 1 of the API should have had a sidebar API however they seem to be focusing on the most trivial things that your average joe apparently wants to. Things like putting an item in the main context menu and toolbars and trivia like that. Given sidebar is Sage’s primary UI definitely need support for that. On the other hand the JetPack devs were reasonably open to feedback when I was looking at JetPack 3 to 6 months ago. Can’t hurt to drop them a suggestion on their discussion group:

http://groups.google.com/group/mozilla-labs-jetpack/t/9e48519115f3a484

By: Peter Andrews

Peter Andrews — Tue, 21 Jun 2011 03:31:51 +0000

True, I could be putting in a few more words about the fixes that are going in. I’ll see what I can do. The problem is that with these maintenance releases, it’s not terribly interesting. I include links to the closed issue reports so that those who are interested can drill all the way down to the code commits if they like. In the case of a minor or major release, I would definitely spend more time talking about the new functionality.

By: Sage Lover

Sage Lover — Tue, 21 Jun 2011 01:50:05 +0000

Thank You!!

By: Bob Myers

Bob Myers — Mon, 20 Jun 2011 17:40:15 +0000

Thanks for fixing this one. Think of this as a suggestion, but it would be cool if you could provide a short blog post on what changed and how you fixed it. Might help create some new maintainers.

By: Peter Andrews

Peter Andrews — Mon, 20 Jun 2011 02:17:18 +0000

Moving away from chrome overlays would be the biggest challenge in a move to the Add-on SDK. I'm not sure there's a way to provide a traditional sidebar yet.

By: pd

pd — Sat, 18 Jun 2011 02:18:58 +0000

Thanks for this, excellent timing. Brilliant! The rapid-release cycle would be a nightmare without the Sage people keeping up.

Re JetPack, it offers shortcuts to old-school components and interfaces AFAIK:

const {Cc, Ci} = require(“chrome”);

This allows access to the full old-school APIs AFAIK, such as I was writing something where I wanted to access to nsIFilePicker’s ability to prompt users for a folder. The JetPack file API cannot do this, only allowed prompting for files. So I did this sort of thing:

const nsIFP = Ci.nsIFilePicker;

var dirPicker = Cc["@mozilla.org/filepicker;1"].createInstance(nsIFP);

and away I went.

Perhaps this approach can help you switch to JetPack even though simple APIs like a sidebar API are not yet available for JetPack?