Option to auto-close (and save) tabs after period of time (like tabmemfree do)
Add an option to close(unload) tab and windows which hanging for too long (for example several hours or days) but leave them in tree as saved, with adequate remark (that they was autoclosed)
UPDATE: leave them by default not in the main tree but in a separate tree, specially for auto-closed items, with an ability to drag windows to the main tree and restore them this way. And autoclose and leave in the main tree if some tab or window itself have some custom marks or note.
Antwort
Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful.
I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.
Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes it might be implemented.
This is not just a hack but a specially supported mode, so you can drag hierarchies back to TO from this file.
Regarding other methods of export/import and synchronize - they are also planed, but i prefer not to promise any exact dates of when.
Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).
I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.
Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes it might be implemented.
Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).
I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.
Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes (or donations ; ) it might be implemented.
Maybe really even as separate tree, specially for auto closed items, with an ability to restore them by dragging in the main tree.
Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).
I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.
Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes (or donations ; ) it might be implemented.
Maybe really even as separate tree, specially for auto closed items, with an ability to restore them by dragging in the main tree.
why someone downvoted it?
I have 50+ tabs, it was using (as I remember) about 2GB of ram, and using about 20% of my 4 core cpu, messing with things like games that use a lot of cpu power;
then, I magically discovered the big green "X" button by side of urls in the tree!
I just retracted the url tree group and click on it and voila! it worked! I can keep all my 7 simultaneous researches and not clog my machine!!!
So, I looked for an option like: keep only the 10 last visited urls loaded in memory (so older tabs would automatically be "big green X button" closed), but I could not find it :(
We could also Pin some tabs to not make part on that last 10 urls list. To protect them.
I dont think they should go to a separate list for auto-closed tabs tho... just make it simple, auto unload them! with a configurable limit of default 10!
unfortunately I can only upvote once..
why someone down-voted is a really interesting question : )
That seems human nature for somebody.
As for request to automatically unload tabs i prefer not to overweight the tool by the rarely used functionality which can be done as separate extension.
There already such addons - The Great Suspender, Tab Mem Free, to name a few. I was tried them shortly and don't find them very useful actually. Anyway such addition must be done as separate extension. It might communicate with TO to save tabs inside it. But i prefer not to add this functionality to the TO itself.
There is already enough people who down vote because it's to complicated for them.
I understand, I just think who downvotes should be obliged to say why, not only here, everywhere, so their perspective could be evaluated too...
I indeed thought it could be another extension telling tabs outliner to do the auto-closing on the big green "X", but I didnt know it could be done.
Anyway, it is aready good, I just go there and click on it what works well.
Concerning complicateness, I guess if you add popups explaining what each button do (that can be disabled at options), and if someone contribute a video, it may help them understand how it works better!
I have no problems at all, it is actually easy to use, and like it very much!
thx!!
The reason I like auto-suspend is simply because of all the memory leaks in different pages. After a couple of days of having certain tabs open, they balloon in memory usage. Auto-suspending them solves this problem without me having to "keep tabs" on them.
The Great Suspender works fine for me, even after saving/restoring suspended tabs.
Chrome 54 added a native tab discard method, allowing the content to be completely unloaded from memory but still keeping the tab in place. Here's an extension that implements it.
Customer support service by UserEcho
Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).
I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.
Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes (or donations ; ) it might be implemented.
Maybe really even as separate tree, specially for auto closed items, with an ability to restore them by dragging in the main tree.