Tree Style Tab
-
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.
-
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.
Been a while since I fired up O12, but I don't you're correct here. IIRC each Opera window was listed with its tabs, but each tab was always a child to the Opera window. In other words you couldn't have a tab be a child of another tab. I also don't think the window display had close buttons, but I haven't fired up O12 for a while so I'm open to correction.
-
If this is not a tree view with tabs with child tabs I must be crazy then.
Yes, there's no visual close button, but you can middle click them or right-click -> close.
Attachments:
-
I have registered just to say,
+1 for Tree Style Tabs. -
If this is not a tree view with tabs with child tabs I must be crazy then.
Yes, there's no visual close button, but you can middle click them or right-click -> close.
That's showing windows stacks and tabs in a 3-level tree view, yes, but what I believe others are asking for here is something more, and significantly different: An arbitrarily deep tree structure, where tabs act as parent tabs for tabs opened from them. (In an Opera 12 stack as in Vivaldi, there is no set parent tab. In the "Windows" panel and in the Window menu-bar menu, the tab stack is just labeled according to the tab most recently called to the foreground.)
Put another way:
-
I know so many people still using FF just for tree style tab.
I is in my opinion by far the best tab management system I have seen.
Please add it. -
As an OPTION. I have tried using tree style tabs and they basically drive me to distraction. I really cannot stand them. So - OPTION, yes. Default, no.
-
+1
It's really hard not to switch from Firefox to Vivaldi already. If Vivaldi gets Tree-Style-Tabbing, it's "bye bye FF" for me. The Email-Client would be a cherry on top, but I can wait for that.
-
It's really hard not to switch from Firefox to Vivaldi already. If Vivaldi gets Tree-Style-Tabbing, it's "bye bye FF" for me. The Email-Client would be a cherry on top, but I can wait for that.
Holy words
+1
-
I'd also greatly appreciate this; coupled with on-demand tab-loading it can also replace/double as favorites.
I would however propose nested tab groups instead of tab trees; i.e.
Node = Tab | Group [Node]
Then it would behave much likes folders and files. New tabs would by default open in the same group alongside the tab they were opened from. I understand that this differs from the proposed tab-as-parent style; a hybrid could allow groups to have a main tab:
Node = Tab | Group (Maybe Tab) [Node]
Visually it could look much like tab groups in Firefox, except they can contain further groups which upon selection would be zoomed into.
-
I could live with your solution, too. But how would you want it to behave when a tab is closed? I would want the children of that tab to have a new group as parent and not drop one level with possibly other tabs (brothers and sisters of the closed tab )
Please Vivaldi-Team, improve the vertical tabbing :cheer:
-
+1 for this!
Seriously, please implement this!
I fear Mozilla Firefox will not support add-ons for tab trees in the future since they are moving away from XUL. If this is the case, probably there will be no up2date browser which supports this kind of feature. (I doubt that Firefox forks want to maintain XUL on their own)
-
Tree tabs(and less importantly a system like panorama) are the only thing keeping me from switching currently
-
Please, add tree style tabs. That's the only reason why I'm using Firefox.