Automatically open windows at startup

[erikrob]

I've been using TabFern for a while and loving it, but there is one thing that is painful : on browser startup I always go through my tree and re-open the same set of windows every time manually. I would love to have a feature that either :
1 - Restores the windows that were open when I closed the browser (and we cannot rely on the browser option to do so because those restored windows would be unnamed ones and I would therefore lose all tracking of my open tabs in the named windows)
2 - Takes a predefined list of windows and opens them up

I'm actually surprised to be the first one to suggest, not finding anything in the current issues... Are people getting around this via another means ?
Thanks

[andr222]

I rely on option 1, windows being automatically reopened. However the names are not kept, and many older versions of the windows are kept, as well as annotations often lost. (Which makes more that the simplist annotations rather pointless.)
What is needed is a means of keeping and restoring the open windows with their names and annotations.
Maybe periodic saving of the tag listes (along with annotations), as is common with text editors, for example.
In my case, automatic suspension of the computer is the main reason the navigator is closed, so automatic periodic saving of tag lists should work well.
The period should be configurable, to accommodate different suppension times.
Another approach would be an option (button) to save all tags and annotations (without closing the windows). (Maybe in the menu lower right ?)

[Darthfett]

I use the built-in session restoring functionality of Chrome, and unfortunately, it means that I basically end up with Saved Tabfern windows, as well as a duplicate "Unsaved" window.

Ideally I'd like my naming to be persistent.

[cxw42]

The difficulty I've had is that, at least in the past, Chrome didn't have its own concept of a persistent window. TF currently makes up a unique ID for each window by hashing the URLs of the tabs in that window (ordered_url_hash).

Since I last touched this part of TF, Chrome has gained the sessions API, which might help. It would need some testing, since it's not clear to me from the documentation whether sessions are always-on or opt-in.