Tree Style Tab
-
While I can see some of the appeal of such a system of organizing tabs, it seems like it would be quite a design headache to figure out how it would cooperate with the existing tab groups. I'm not sure the two could play together without becoming something of a muddled mess.
-
While I can see some of the appeal of such a system of organizing tabs, it seems like it would be quite a design headache to figure out how it would cooperate with the existing tab groups. I'm not sure the two could play together without becoming something of a muddled mess.
I think it is may be superior to tab grouping because it groups automatically while still allowing manual control. Perhaps grouping scheme can be made an option?
-
While I can see some of the appeal of such a system of organizing tabs, it seems like it would be quite a design headache to figure out how it would cooperate with the existing tab groups. I'm not sure the two could play together without becoming something of a muddled mess.
I prefer Tree Tabs over grouping if it comes to it. I don't see the need to group tabs if i can stack them under a tree where i can expand/close each branch as i need to.
-
Also a big fan of TreeStyleTabs in Firefox: it is much cleaner than grouping, also the way it is hierarchical it can make your workflow much more fluid.
-
Also a big fan of TreeStyleTabs in Firefox: it is much cleaner than grouping, also the way it is hierarchical it can make your workflow much more fluid.
Yeah. Really DON'T like tree style. If it were to be introduced, eventually, I would be happy to see it as an option rather than the default way tabs were grouped.
-
I think it would be helpful for the developers, if you could share what advantages do you feel grouping has over tree style, also what is it, that you don't like in the tree style solution. In my experience everyone loved it, after I show them the extension in Firefox.
-
My personal reasons are these:
-
I can see all of the previews in a stack merely by hovering, and select one. Treeing cannot do this - at least, I've never seen a tree-style app that could.
-
Tree style apps appear to be incapable of turning off treeing, and I inevitably wind up with "trees" of tabs that, really, have nothing to do with each other - because I do not naturally pay attention to which tab or tab family I am opening a tab from. The resulting random indentation (as I use vertical tabs) of tabs for no sound reason irritates me.
-
-
My personal reasons are these:
- I can see all of the previews in a stack merely by hovering, and select one. Treeing cannot do this - at least, I've never seen a tree-style app that could.
when the tree is "closed" you can see a list of all tabs under it by hovering,
I personally don't like previews/screenshots of that tabs,- Tree style apps appear to be incapable of turning off treeing, and I inevitably wind up with "trees" of tabs that, really, have nothing to do with each other - because I do not naturally pay attention to which tab or tab family I am opening a tab from. The resulting random indentation (as I use vertical tabs) of tabs for no sound reason irritates me.
You'r using it wrong (or a bad configuration), as i don't have this problem.
-
- Tree style apps appear to be incapable of turning off treeing, and I inevitably wind up with "trees" of tabs that, really, have nothing to do with each other - because I do not naturally pay attention to which tab or tab family I am opening a tab from. The resulting random indentation (as I use vertical tabs) of tabs for no sound reason irritates me.
I can't argue with that: if it is implemented badly, it is more pain than an extra. Fortunately TreeStyleTab extension handles it perfectly - it just works under my hands, but if you need something extra you'll also find many options to customize it. Just give it a try. As many-many users say it in the Chrome forums: this extension is one giant reason that they stick with Firefox.
-
I used TreeStyle with Firefox for about a year. In fact I have it installed now, as the "least objectionable" way to have side tabs in Firefox. I have turned off everything that could cause a child-parent tab relationship, and the best result I can obtain is a choice between having "child" tabs (which I don't want) either indented or separated by a blank space from the next "tree" (which I don't want.) I don't want trees. Yet, using this extension, they cannot be fully turned off.
It's OK with me if any tab generated by a link appears next the the tab that owns the link, and any new tab appears at the end of the tabs. But beyond that, I dont want ANY automatically-created relationship between tabs.
And, btw, hovering a closed tree only shows a single preview, not a preview of all tabs in the tree, and offers no ability to select from among them.
I prefer stacking, done by me, not automated.
-
+1 for having this as an option.
Also, tab stacking is broken with side tabs if you reduce the height of the tabs to remove the thumbnail (As any sane person would) making the current tab stacking implementation useless anyway.
-
This is one of the major points that is keeping me from switching to Vivaldi from Firefox, and I'm certain that the browser will gain more defectors if this option were to be implemented.
-
+1 for having this as an option.
Also, tab stacking is broken with side tabs if you reduce the height of the tabs to remove the thumbnail (As any sane person would) making the current tab stacking implementation useless anyway.
I don't find this to be true of tab stacking on the side. What problem are you experiencing?
-
I use Tree Tabs on Firefox, but I can't tell which is better, the Vivaldi-style stacking or the tree structure. There are cons and pros. But, with optional multiple "views" of tab groups, you can switch between the two styles!
First, you allow for nested groups: you can have groups contained in a parent group.
Then, in the "tree view", you have the Tree Tabs of Firefox. In the "stack view", you recover the present Vivaldi behavior (plus possible nesting). (But, I'm not sure how to show nested groups in the stack view.)
Automatic grouping is a separate issue. What I miss from Vivaldi is the ability of auto stacking. What I do like about Firefox's Tree Tabs is that the grouping is automatic. (And, if you want, you can move tabs around between groups, of course.)
So, all in all, what I would like for Vivaldi is
[ol]- A form of automatic grouping.
- Optional, multiple "views" of the groups as described above.
[/ol]
-
@Sajadi:
Would love to see an option like that, could bring quite some frustrated Firefox Users towards Vivaldi!
If it was an option, what do you do to existing stacks/trees when a user switches modes? And what do you do if a saved session from one mode is opened while in the other mode? You could flatten a tree to a stack easily enough I guess, but which tab do you automatically promote to root tab when converting in the other direction?
-
I don't understand the parts of the discussion about stacks vs tree view. Doesn't Presto Opera have both at the same time? I'm currently looking at my "Windows" panel in O12 and it's 100% a Tree view.
-
@caladis:
If it was an option, what do you do to existing stacks/trees when a user switches modes? And what do you do if a saved session from one mode is opened while in the other mode? You could flatten a tree to a stack easily enough I guess, but which tab do you automatically promote to root tab when converting in the other direction?
You can have as many root-tabs as you want. These root tabs are at the top level of the tree.
I get that; what I'm asking is if you have two tab groups {a,b,c},{d,e,f}, and you then switch to tree mode, which tabs do you promote to "root" tab status? Should the program somewhat arbitrarily pick the first in each group (a and d)? Or create two new blank/speed-dial tabs g and h, so it becomes g{a,b,c},h{d,e,f}?
Either could be done, but it's something that would have to be decided upon, if they did decide to support two different tab taxonomies (tabsonomy? – ugh, maybe not, the world doesn't need yet another gratingly cutesy portmanteau =P) in parallel. It might also be appropriate to warn the user, on opening a tree session while in stack mode (or when switching modes) that the hierarchical organization of the trees is being flattened to tab stacks.
-
@caladis:
If it was an option, what do you do to existing stacks/trees when a user switches modes? And what do you do if a saved session from one mode is opened while in the other mode? You could flatten a tree to a stack easily enough I guess, but which tab do you automatically promote to root tab when converting in the other direction?
You can have as many root-tabs as you want. These root tabs are at the top level of the tree.
I get that; what I'm asking is if you have two tab groups {a,b,c},{d,e,f}, and you then switch to tree mode, which tabs do you promote to "root" tab status? Should the program somewhat arbitrarily pick the first in each group (a and d)? Or create two new blank/speed-dial tabs g and h, so it becomes g{a,b,c},h{d,e,f}?
To solve this problem, the internal data structure should always be a tree. Even in the stack-view mode, the data structure would know which node is the root of each group. Problem solved, I think.
-
To solve this problem, the internal data structure should always be a tree. Even in the stack-view mode, the data structure would know which node is the root of each group. Problem solved, I think.
Unless I'm misunderstanding you, I don't see that as being consistent with the current stack model. Currently, the user selects two or more tabs, then right-clicks and clicks "New Tab Stack with Selection". In doing so, the user isn't making any assertion about one of the tabs being a primary tab.
-
+1 for this feature as well. Presently I'm using Palemoon as my main browser, but I almost always have Vivaldi open as it does a lot of things better (eg: YouTube is much smoother). Right now the single reason Vivaldi hasn't been elevated to my main browser is because of this feature.
If you get used to Tree Style it really does add to your browsing experience. A common example with me is if I'm doing research. The ability to open links in new tabs and have them into a tree structure means gives the following advantages:
- I can see instantly how I reached a given tab (helps with keeping the train of thought).
- The tabs are already organised, no fiddling from me required.
- This allows quite a large number of tabs to be open and still be easily navigable.
Let me illustrate with a real life example from work yesterday. We had a tracker fitted to a reefer trailer and, for reasons I don't understand, it turned the reefer's display from Celsius to Fahrenheit. Not the biggest issue, but annoying nevertheless. So I had a definite research question that needed an answer (i.e. how to change the settings back). So I naturally tried to find online manuals for the reefer's control panel. I would scour different forums looking for people who discussed the unit. I learned that I needed to access something called the 'Guarded Access Menu', but I didn't know how to do that. During the research I had come across people making reference to this menu but I did not know the significance of it at the time, and thanks to all those webpages being in a Tree Style I could get back to them in a few clicks. Piecing together what people did with other models allowed me to work out the button combination I needed for our own reefer.
The above isn't the most important example in the world. But it is an illustration of Tree Style greatly adds to the browsing experience. I use this functionality so much that if I have to use someone else's computer I will run a portable version of Palemoon with this extension off a USB key.