Talk about add-ons and extension development.
this is awesome ! i slowly got really sick of TMP's sessionmanager that screwed up in conjunction with 'Restar Firefox'. Finally a sessionsaver that works reliably and also restores cookies and form data. Great work.
@Recall: There will never be a (hidden) pref to hide a menu entry. Ever. That'd just mean more code and one decision more for the user. Additionally, since I figured out how easy it is to create an Options dialog, I'm no fan of hidden prefs any longer - and I simply don't see an entry "Hide Session Manager's menu entry" fit into that dialog (which BTW has been nicely refactored). If you don't like CSS, try MenuManipulator or a similar extension instead (I suppose that this is not the only menu item you'd like to hide - so better get a universal solution from the start).
@C@rb0n: The typing lag should be every 10 seconds (unless you lowered the minimal saving interval) - if there is any. I've improved performance somewhat more, but there's hardly any place I could further cut down without losing accuracy (I'm already doing quite some caching to keep the impact minimal). I now measure an impact of around 100 to 120 ms per saving/closed tab with 3 windows à 10 tabs opened (on a machine about as performant as yours) - that should be barely noticeable. Now my concern is restoring...
I have one window open with about 35 tabs and a second window with only one site.
I close the second window and then the first window. I get asked by FF if I want to close all 35 open
tabs. I click on yes.
When I start FF again, I get asked which session I want to restore. I click on Previous Session and
only the window with the 35 tabs opens. Not the second window or any other windows I had open.
With Sessionsaver, this worked.
Do I have to explicitly save the whole session before closing all windows?
PS: zeniko, could you include a date in your changelog? Would be nice to see how fast you improve this extension
problem restoring all windows..
i have two windows open (each in a different virtual desktop). SM is configured to <back up current session> at shutdown. i restart, select [Previous Browsing Session] and only one window is opened.
also, the problem i reported above regarding opening a named window|session from a running window and its tabs not opening but coming up blank, continues but is sporadic. just now, trying to open a named window caused it to come up blank but positioned right; on closing that window and trying again, the tabs came up but the position was wrong. and, bizarrely, closing and opening the new window a 3rd time made it come up right, with both tabs and position!
difficult to have confidence with such inconsistent behavior.
also, one \sessions file is named A and another B.session (also a backup.session), normal? is there a diffence saving a name as window then saving it as session (with one window) or the reverse?
but the new options dialog is very nice, i might even say user friendly.
[edit: huh, i was just writing the same thing as the post above was entered..]
Nice job on the options dialogue exactly as i had envisaged it.
Guess I will be d/loading another extension ( trying to keep mine to a minimum so less conflicts, thus the reason for the preference request. )
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:1.9) Gecko/2008051206 Firefox/3.0
@Tahattmeruh: You have to distinguish between closing your browser window by window and closing all windows together. You close window by window which will quit the browser when the last window is closed. Now, Session Manager only restores what was open when the browser actually exited. If you wanted both windows to be restored, quit through File -> Exit (which closes all windows together). SessionSaver stores closed windows for a few seconds and saves everything should the browser exit in that time. I originally considered this to be a bug (getting windows restored I had closed right before closing the browser) and now just disagree with this design decision...
As for the changelog dates: that would be too depressing. There are currently minor releases about every day and major ones about twice a week. Since version 0.1 is less than a month back, you can figure out the rest for yourself...
How about saving all the closed windows and clear the list if a new site is opened?
So closing all windows manually will restore all windows again.
It would be nice if the closed windows list was saved on a crash and also at shutdown as a current session backup, especially in my case where I never have other actual windows open.
As it is, I only have preserved what is in the current window saved (as some others have noted).
I have Session Manager configured to Replace Existing Windows.
And zenico, with a little tweaking, I am able to overwrite the current window with undo closed windows without using ctrl-shift
Nice work on the latest release, btw.
No. If you close a window, you just close that window unless it was the last one and the browser is closed together with the window. If you want several windows to be restored, you'll have to explicitely say so (by quitting through File -> Exit). This extension won't try to second-guess your intentions. You might thus want to consider to adapt your habits to a more precise expression when interacting with your dumb-as-a-stone computer.
@dougeeebear: The list of closed windows is preserved when Firefox crashes. If you also want it to be preserved after regular shutdowns, you'll currently have to manually remove the line this.clearUndoData("window", true); after "quit-application" in sessionmanager.js or explicitely tell Session Manager to store the current session. And for the next release, I'll think about adding a pref for persisting the Undo Close list at shutdown...
Preserving closed windows worked, but it worked too good
I was expecting them to be preserved in the [Previous Browsing Session], but they were preserved at startup, which is undesired.
ah i recall many pages back a restart bug - would getting rid of MTLI solve it? i'm on the verge of dumping that anyway..
but now i can't recreate it. as i said it's sporadic, seems if i don't start the second window but maybe do a lot of restarts or work with the first, after time trying to start the second will fail.
i won't bug you again unless i get some diags that are useful.. but i've never seen a sessionmanager error in the console.
I can't count the times that I was creating a test case to present a 'bug' andit's possible cause/fix and then posting it (or customize SM for my own use), only to find that you just either fixed it or added the the feature.... hehehe.... Kudos....
Thanks so much, zeniko. Sorry for being so demanding.
Last edited by C@rb0n on March 7th, 2006, 7:12 pm, edited 1 time in total.
ok, here we go. did some browsing with just one window, then tried to open the second, which failed. first several console errors.
That's the same error I reported when xul caching is disabled. Probaly as zeniko said, it is taking the window a longer time than anticipated to set up for some reason (even though zeniko coded to loop if the window isn't set up/exsists yet). So far I can't figure why the loop exits yet the error persists....
On my machine I manually increase the value from '100' to '2100' in the crashrecovery.js (components folder)
if (!aWindow.getBrowser || !aWindow.getBrowser())
aWindow.setTimeout(this.restoreWindow_proxy, 2100, aWindow, root, aOverwriteTabs);
Who is online
Users browsing this forum: No registered users and 3 guests