Talk about add-ons and extension development.
The current release, <a href="http://www.haslo.ch/zeniko/software/sessionmanager.xpi">Session Manager 0.2</a>, adds a automatic tab reloading and a toolbar button for access to all functions/settings (which still needs an icon on its own).
If you want to control Session Manager with the keyboard, you can add the following keyconfig keys:
* Save the current session (same as hitting the toolbar button):
* Load a specific session:
* Open the session folder:
* Display the toolbar button's drop-down menu:
Any plans to support SeaMonkey?
Sure, as of <a href="http://www.haslo.ch/zeniko/software/sessionmanager.xpi">v0.2.2</a>. However, as a side effect of SeaMonkey's hideous installation framework, you'll have to install <a href="http://www.haslo.ch/zeniko/software/crashrecovery.xpi">Crash Recovery</a> first.
Fantastic! I can't say enough good things. Simple to use, intuitive and streamlined... Excellent & Thank you!!
I noticed there's prefs under extensions.sessionmanager.* and extensions.crashrecovery.*. A minor nit to be sure, but maybe it'd be best to have 'em all under the same prefbranch so people looking around in about:config are able to see everything by filtering for the obvious (session(manager)).
sessions/* seems like a custom file format. I've no preference here, but RDF may be a bit simpler to manage. TabMixPlus uses RDF (sessions.rdf), SessionSaver 0.2d just uses prefs.
The scroll position stuff is nice, but doesn't appear to handle frames. I've been working on a (private) extension to workaround bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=215405">215405</a> and have some of that handy, you'd just need to find a way to store it...
(probably similar to sessionsaver 0.2d)
Is there a way to disable saving and restoring of post/form data? I see the .postdata pref, but at first glance don't know if it's for internal usage or what. The main reason I ask is that ss 0.2d seems to have (or has had) problems with slow script dialog when doing file uploads. If the data is above a certain size (say 250kb) and is not already ignored, you may want to do that. Some boolean prefs to disable one/both may not be a bad idea...
I'm not sure if you're aware of this, but session saving in one form or another is supposed to be coming to Firefox 2.0 and work will be starting shortly. I'm sure everyone would appreciate code contributions. Bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=36810">36810</a> appears to be the main one, but it's listed under suite, so I'm not real sure... I've also seen bug <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=159357">159357</a>. Anyone??
This is intentional since I intend to keep the session saving component (Crash Recovery) independent of the session managing front-end. And obviously this pref-splitting shouldn't confuse anyone who dares to load about:config (which isn't for Joe User anyway).
I originally tried to use an RDF format similar to TMP's, but handling the data in that form was so much of a PITA that I settled on a specialized and yet extensible text format. These files can be parsed very easily, should it really be necessary. OTOH, the problem with preferences is that saving a session can quickly double prefs.js, and an additional import/export facility would be required for moving sessions around.
There are still some things missing, and some other things will never make it at all. This particular issue will be fixed in the next release.
Currently the .postdata pref indicates up to how many bytes of POSTDATA should be restored (-1 = all of it, 0 = none). In the next release, it will also limit POSTDATA saving (for better performance).
Work's already started at wiki.mozilla.org (here's the current status).
Unfortunately, this restores only the last active window, discarding other windows. Is there a setting to resolve this? I have set extensions.crashrecovery.resume_session to true
Also, the Sessionmanager component does not work. All it shows is "Session Manager" with an empty submenu under the Tools menu.
Do you close all windows in sequence or are you quitting through File -> Exit (only the latter will restore all windows)? And is this with Firefox or SeaMonkey?
That was an issue with v0.2.2. Make sure that you've got v0.2.2.1 installed.
SessionSaver (0.2) checks the window closes times and appends the session history if it falls under a certain threshhold.
If you kill the process, all windows are properly restored.
I'm using Firefox 188.8.131.52, and I did File -> Restart (because I have the "Restart Firefox" extension installed)
I am using v0.2.2.1
The first issue is due to a "bug" in "Restart Firefox": it never calls canQuitApplication() (which notifies all extensions of the shutdown). I recommend to contact its author about that issue.
First one word of caution: SessionSaver's code is not open-source. Although it is publicly available, it can't be used or even discussed without admission by rue.
That beside, I didn't know about that feature. Although having observed it, I assumed it was a bug. Anyway, I prefer not having to try to be clever about the user's intentions. That feature won't thus make it into Crash Recovery (for now).
That was taken from 0.2 (not the rewrite). There's no license of any sort in the original, merely a comment at the top of each file stating the version and authors name, so public domain.
I'm not quite sure what to make of this, but if it is how you say it is ... seems ludicrous.
I rarely have more than one window open anyway, so that's not an issue for me.
Thanks. I have sent the author an email.
All right. Try <a href="http://www.haslo.ch/zeniko/software/sessionmanager.xpi">v0.2.3</a> then. If it still doesn't work, you might want to try a clean profile...
Who is online
Users browsing this forum: No registered users and 1 guest