Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support tab groups #2

Closed
gdcl opened this issue Dec 5, 2020 · 2 comments
Closed

Support tab groups #2

gdcl opened this issue Dec 5, 2020 · 2 comments

Comments

@gdcl
Copy link

gdcl commented Dec 5, 2020

Tab groups seem to be a perfect match for what you built here. Consider being able to state in a node in the tree whether you can it grouped under a window, or in a tab group. Both would be useful and it would bring down the total nr of windows if you want to bring up a whole set of pages at once.
Great project.

@tconfrey
Copy link
Owner

Hi @gdcl,
First, I'm sorry I missed your issues earlier, I use git on the command line and didn't think to monitor for issues posted on github.

You are completely correct that tab groups are a good match for the BrainTool ui! I got a lot of good comments and complaints about the way BT handles Chrome windows and have been working on improvements for the last few weeks. I'm close to completion and hope to have a version out to some alpha testers early next week. I'll post details on the discussion group and you can LMK if you want in.

Tony

@tconfrey
Copy link
Owner

tconfrey commented Mar 2, 2021

Hi @gdcl ,
The new 0.7.0 version of BrainTool that just went live in the Store supports a global preference for whether new tabs should open in dedicated windows per tag (the initial model), or tab groups per tag, or just as a new tab in the default working browser window.

At some later point it may make sense to allow this mapping to be set on a per-tag basis but for now I think the global setting does the job. I'd love your feedback on the result.

NB one issue I have is that the Chrome Tab Grouping api is not yet fully functional in production Chrome so I can't name the tab groups appropriately. The upcoming 89 version of Chrome is meant to address this at which point I'll name the tab groups appropriately.

Regards,
Tony

@tconfrey tconfrey closed this as completed Mar 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants