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

add tabs to closed windows #25

Open
timoreimann opened this issue Jan 29, 2013 · 2 comments
Open

add tabs to closed windows #25

timoreimann opened this issue Jan 29, 2013 · 2 comments

Comments

@timoreimann
Copy link

I often run into situations where I'd like to add one or two tabs to an existing but closed window. The workflow to follow then is to open that window, move the tabs into, and close the window again. This can be quite tedious and time/resource consuming with windows containing a lot of tabs.

I'm not really sure as to how the perfect UI should look like; something that should work and not too hard to implement would be a button or link next to each saved window in the session list (which may possibly only appear on mouse over) that says "add current tab" and stores the current tab into the window.

@nickbaum
Copy link
Owner

I totally sympathize with this request, as I regularly run into the same situation. However, it's not clear to me how to add this feature without adding more complexity to the interface than it's worth.

I know it's tempting to add an extra menu for each window that would allow things like adding a tab, renaming, merging, etc but this has a big impact on the perceived complexity for a new user, and also adds a lot of complexity to the code base. I'm not saying I would never do it, but I'm reluctant to do so for the time being.

@timoreimann
Copy link
Author

The UI will probably be the most challenging part. OTOH, I could imagine two approaches:

  • Use a few number of icons (like three or four) for the most needed functions, just like the close icon available now. Additional functions may be hidden behind a drop-down menu.
  • Support both a simple and advanced UI frontend switchable via an options page. The latter would be targeting power users that seek out for a lot of features.

Either way, code complexity will increase. IMHO, the way to deal with it is expectation testing (i.e., unit testing, UI testing, and others) which will be very helpful for future development anyway.

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