Tree Tabs

JuniorSilva30

@JuniorSilva30 Sorry, no. But I'm working on compatibility for Firefox (I'm almost there). So basically I will cover Opera, Vivaldi and Firefox. You can, as @luetage said, open my extension in a new tab and detach it to a new window, but it's not that great this way. There are already extensions like "outliner", "tidy sidebar", "tabsman", "sidewise" and many others that do that (open a popup window), because there is no sidebar space in chrome.

You can tell what you think about lack of sidebar/sidepanel/webpanel (all are the same thing) directly to google here

Ok, I got it! Thanks for the info!
If you publish this add-on to Firefox, it will have many users, the extensions that do the same are being abandoned because Firefox will change in version 57, so its add-on would conquer users. I hope it does not take too long.

JuniorSilva30

@luetage said in Tree Tabs:

@JuniorSilva30 Chrome has no panel. You would need to run it in an additional window beside the browser. Some extensions do that already on chrome.

Thanks for the info! I have already tested extensions that does this, it is not practical to have two windows open on a small screen.

kroppy

@luetage Yup, only choice is to email google dudes to personally persuade them, or open another request (which probably will be just closed as a duplicate).

kroppy

Update:

Some small fixes in options page (mostly translation and css compatibility with Firefox)
90% Firefox compatibility, but I give it in a separated zip, because manifest.json is a little different.
Added option to treat unparented tabs as children of the active (opened from bookmars or from ctrl+t shortcut)

kroppy

@pina_coladas Sorry, for late response. Been busy (as you can tell) and tried to post only essentials, but now I can relax a bit more and respond to missed questions. About a year ago I've asked, on Opera's forum, how people would prefer tabs to be arranged, just in trees or in folders, but nobody seemed to be interested, so I decided to make just trees, because TST has the biggest user base on Firefox add-ons page and it will stop working with Firefox 57, so my decision was to make an alternative for all those folks that will cry for a big loss. Sorry about that. I can change that in the future, or make a branch extension, but take it as a grain of salt... Actually I still have a working prototype which was simpler to implement with folders+tabs structure, where tabs can be dropped only to folders, not to tabs. Structure is like folders and files in explorer, which I think is more logical.
And heck I used Pano for years, it was my favorite extension for Firefox, until mozilla decided to ditch panorama tabs grouping, on which Pano relied.

kroppy

If you publish this add-on to Firefox, it will have many users, the extensions that do the same are being abandoned because Firefox will change in version 57, so its add-on would conquer users. I hope it does not take too long.

@JuniorSilva30 Done. Surprisingly they accepted it really fast.
Here is the link. Obviously it requires Nightly or Dev build to run, since Web extensions are not enabled in FF 53 yet. And it won't be until FF 57 somewhere in November.
https://addons.mozilla.org/en-US/firefox/addon/tree-tabs/

kroppy

@GHM113 Did you check out the options page? There is no direct access to options from addons page (which is weird, since options entry is present in manifest.json), click with right mouse button somewhere on tabs (in the sidepanel) and click on Settings at the bottom of the menu.

The option you should check is "append orphan tabs (opened from +, shortcut or bookmark)", set it to "treat as active's child"
"once reached tree depth, place tab on the same level, but" set it to "after parent"

There are more actual bugs present right now, for example most buttons in toolbar under the "wrench key" shelf are not working, since Firefox has a little bit different API and they don't give access to "about:" pages.
And others like, no way to hide Tabs Bar from Web extensions (at least not yet). You must use another (standard bootstrap) extension to do that, for example "Hide Tabbar", works a treat.
There is no ::webkit:: scrollbars equivalent css rules in Firefox, so scrollbars are standard. Maybe I will find a way with jquery.
But most critical right now is that very often trees are lost after Firefox restart, it might be some performance issues with jquery, but I'm not 100% sure, I'm working on it right now (debugging in FF is a b*tch, since I have to pack extension on every change in code and restart to see if trees are lost, it wouldn't be the case if it was not after restart). It will take some time until it will be really usable in Firefox, but I'm getting there, so be patient, hopefully in few weeks I will make it working perfectly

Hope that helps.

JuniorSilva30

@kroppy said in Tree Tabs:

If you publish this add-on to Firefox, it will have many users, the extensions that do the same are being abandoned because Firefox will change in version 57, so its add-on would conquer users. I hope it does not take too long.

@JuniorSilva30 Done. Surprisingly they accepted it really fast.
Here is the link. Obviously it requires Nightly or Dev build to run, since Web extensions are not enabled in FF 53 yet. And it won't be until FF 57 somewhere in November.
https://addons.mozilla.org/en-US/firefox/addon/tree-tabs/

Great complement! You can be sure that you will have a lot of users over time!

kroppy

@GHM113 Oh, you are right. I'd like to know how TST does that. Probably "overwrites" global ctrl+tab hotkey. Until I find a way to do that as well it's now controlled by the browser, tabs are switched in opening order.

kroppy

@JuniorSilva30

kroppy

@GHM113
Naaah, wait, I have to clarify it a little bit. I'm not modifying anything. Ctrl+tab is a global key in firefox, it's not getting the order that is inside of the sidebar, so it's switching tabs in the order you see on the tab bar at the top, not in order that is in the sidepanel. If you take a look at the Firefox Tab bar at the top, you can have something that is completely unrelated to your trees. For example if you move tabs around you will see that tabs stay at their position in the sidepanel, and the other way around, if you move tabs in the trees, tabs at the top wont move. That is why I have to implement my own alt+tab. And this is exactly what TST is doing.
Hope that explains things a little bit. Of course this same applies to Vivaldi and Opera as well.

And by the way:
If you need order [parent tab][1][2][3][4], just set "append children tabs at the bottom" in options.
I think this is what you need:
http://imgur.com/a/ONGXq

TMSxVivaldi

You are a life saver!

kroppy

@TMSxVivaldi No problem, if you have any questions I'm always available to explain, fix and whatnot.

kroppy

I have two new problems, one is that, when I updated extension for Firefox, stored options were lost. I'm not sure why. Trees are there, but selected theme and various other options were on default. I will have to investigate what is going on, since in both Opera and Vivaldi all options are preserved just fine.

luetage

I didn't know Tree Tabs was on the Opera add-ons site. This means we can add it as .crx extension. What I don't know is if Opera add-ons update automatically. I run one (and have run a couple) of these, but I can't recall if they ever updated themselves when installed in Vivaldi.

iAN CooG

I think only officially downloaded extensions from chrome store gets updated automatically

luetage

@iAN-CooG I think so too, but in fact I don't know, there's a difference.

kroppy

@luetage said in Tree Tabs:

I didn't know Tree Tabs was on the Opera add-ons site. This means we can add it as .crx extension. What I don't know is if Opera add-ons update automatically. I run one (and have run a couple) of these, but I can't recall if they ever updated themselves when installed in Vivaldi.

There is extra header in nex file and extra things in manifest.json for opera, if you simply change .nex to .crx, Vivaldi will not allow you to install. But you can try to unzip, and pack it back in Vivaldi. Then you will be able to install, but you still wont be able to update. Each extension has its private key assigned by Opera, they repack it, after that there is a small hash like id added to manifest.json file. Even I don't have access to the original key, as I said before they put it somewhere in the header of the file. It would be cool if it worked tho, I would not have to upload updates to google drive each time, and you would have auto updates.

kroppy

@pina_coladas Yeah I know what you mean it would be a beast of a tabs manager.
I have to finish what I have here first, it's still incomplete and buggy. There is no "simply" adding features at this point, it would mean a rewrite of half of the code. Might not be a bad idea, but getting to the point with what I've learned from my first vertical tabs extension which took me almost 2 years, this time it was only 3 months of hard work often till 4am, so maybe next fork may take less. Few months of allnighters and it can be done. Just kidding or maybe not But I will need a little break before starting.

luetage

@kroppy Yeah, makes sense, but it's still nicer operating it packed instead of loading it unpacked. How about putting it on github so that we can just pull it with command line, instead of downloading it from google drive?