Open loligans opened 2 years ago
I think this is redundant since it is not Sidebery's purpose to become another Auto Tab Discard. Also Sidebery has a fantastic feature to automatically unload folded groups after X minutes. So I think this featureset is already good.
I think this is redundant since it is not Sidebery's purpose to become another Auto Tab Discard. Also Sidebery has a fantastic feature to automatically unload folded groups after X minutes. So I think this featureset is already good.
I disagree; sideberry already implements means to unload tabs after an interval X (on collapse of a tree, but the base is there). So why shouldn't sideberry also have such one feature to automatically unload Y amount of tabs after X time of inactivity? Plus, you can already unload tabs manually with sideberry -- so I'm not entirely understanding your sentiment...
Sideberry's main feature is the ability to essentially hoard tabs (which I am very thankful for, given my work environment). Implementing a similar thing to Auto Tab Discard with the extremely clean and intuitive way of sideberry's configuration page can make it the add-on for tab hoarders. I'm not a huge fan of fragmentation where it is not necessary, and I think here to have yet another add-on to control tab unloading instead of having it also in sideberry does no real good.
So why shouldn't sideberry also have such one feature to automatically unload Y amount of tabs after X time of inactivity?
Because ATB already does this already with far more features including regex whitelists. If anything Sidebery could add something ATB doesn't have.
Because ATB already does this already with far more features including regex whitelists.
Who's to say that this won't be the case? The OP is as generic as it can be; it leaves room for discussion and other features (like we already do).
However, to me it seems unreasonable to say "this won't be added. Ever", when a baseline is already established (tabs can be unloaded manually) -- that's why I am still not quite understanding where you're coming from. If you could please explain your position a little more detailed? Don't get me wrong, I'm not saying your views are wrong or flawed, to me though it currently looks like you just don't want this suggested feature (the actual implementation is irrelevant as of now) because somewhere someone already made it with some extension -- to which I can only really say, well, don't use Sideberry, because tabs are already a thing in native UI.
I hope you can understand my confusion about your stance on this feature.
Kind regards
@l-zeuch Your comparisons are logically fallacious.
Auto Tab Discard (ATB) is a typical extension people install. Try it with Sidebery, end of story.
Sidebery has to draw the line somewhere in terms of feature inclusion otherwise it will be way too many features in one package.
This is why TST separated out into multiple extensions: the developer got tired of managing so many features in one package.
Thank you for your quick reply!
Now I see and understand your point of view -- and I do fully agree (now), scope creep is the worst thing that can happen to a software.
Summa summarum, I was heavily misunderstanding you, for which I apologise :-)
It would be nice if sidebery would allow tabs to auto unload after a period of time of inactivity