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

Suggested enhancement: Pin/Unpin Bible tabs - just like in modern tabbed browsers #989

Open
DavidHaslam opened this issue Mar 17, 2020 · 6 comments

Comments

@DavidHaslam
Copy link

DavidHaslam commented Mar 17, 2020

It occurred to me that this could be a cool enhancement, one that would obviate a lot of hassle in finding the rightmost tab, and switching between tabs separated by more than the available display width.

Each pinned tab would require mouse-over tool-tip to display the module Name (or Abbreviation), the current location reference, and (underneath) the module Description.

@DavidHaslam
Copy link
Author

Another cool feature of tabs in modern browsers is that their order can be rearranged by moving any tab using the mouse for drag and drop. This too would be a useful enhancement for Xiphos.

@karlkleinpaste
Copy link
Contributor

i'm at a complete loss to understand what is intended by this.

tabs already identify the bible and verse.

un-pin in what sense? do you mean "remove from the main display, into an independent window," as though opened from the module list in a separate window? there is a semantic consistency problem in that separate windows opened from the module list are single modules, not a bible+commentary+dictionary set.

if so, it's possible...but let me tell you, the code to do so would be horrendous, due to assumptions baked into tab management long, long ago.

@greg-hellings
Copy link
Contributor

@karlkleinpaste

In a browser a "pinned tab" is still in the same window, but the size of the tab display is reduced to its minimum size: usually just the favicon. All included text is removed from the tab, and all pinned tabs usually get grouped on the far left of the browser window. This both reduces the size of tabs, leaving more room for other tabs, and keeps a location for frequently used tabs. Normally the mouse-over close button is also hidden to avoid a pinned tab being accidentally closed. You would either have to first unpin and then close, or context-click and then close.

Normally your most frequently used tabs would be pinned: for instance your email, your favorite language docs, and maybe a few others that you're always going to be using and you can readily identify by their favicon.

Personally I've never seen the usefulness of it, but I know lots of people do use it. I don't know what the equivalent of a favicon would be in Xiphos' context, though. Maybe just the module identifier "KJV", "ESV"?

The idea of being able to reorder/rearrange tabs is a potentially valuable one, though.

@DavidHaslam
Copy link
Author

DavidHaslam commented Apr 16, 2020

@greg-hellings
Thanks for explaining the pinned tabs concept to @karlkleinpaste

Some browser users have far more tabs open than just a few.
In Brave, I currently have 34 pinned tabs, and 4 unpinned tabs.

In Xiphos, I currently have more normal width Bible tabs open than will fit across my laptop screen with a maximized app window. It would be much nicer to be able to select the rightmost Bible (often the most recent one that I'm testing) by means of a single click, rather than having to use multiple clicks to shift all the other tabs to the left until I find it.

Pinning the current tab could move it to the left (as explained), and making it narrower and with a tool-tip description would be a further benefit.

@DavidHaslam
Copy link
Author

@LAfricain
Copy link
Contributor

Something else in the same idea, it's to move the tabs, by instance to take the last and move it in the first place. Or, why not, unpin a tab to have a "free" windows, like LibreOffice can do.

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

4 participants