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

While in the reading screen, navigate to the next book and to the previous book #585

Open
Inquisitor-Ignotorum opened this issue Feb 17, 2025 · 0 comments

Comments

@Inquisitor-Ignotorum
Copy link

Inquisitor-Ignotorum commented Feb 17, 2025

Configuration: Windows 10, Lute v. 3.9.5 installed via pip

Hello. I always have several books on the Home screen and do reading from every one of them on a daily basis. To make navigating to each book easy and fast, I always open all the books before I start my daily reading, with each book being in its own tab. I then navigate to one book's tab, then do as much reading as I want to do from that book, then close that book's tab and move to the next tab, which contains the next book. I recently started thinking that it would be nice if there were a way to navigate to the next book and to the previous book of the user's collection while being on the reading screen. This way the user can save time and effort because, once they finish their reading for one book, they can immediately move to the next book. They will not need to go through the entire process of returning to the Home screen and then finding and selecting the next book, and they will not need to open many tabs for their books because everything could easily and quickly be done from one tab.

It seems to me that an easy way to implement this would be to include two buttons in the reading screen's hamburger menu. Clicking one of the buttons would take the user to the book located immediately above the current book while clicking the other button would take the user to the book located immediately below the current book. To make things even more convenient and easy for the user, each of the two buttons could also be associated with a hotkey.

I guess that, if the book in the reading screen were a book from the Book Archive, then the two buttons would have to target the book collection of the Book Archive instead of the book collection of the Home screen.

It seems that the only drawback of this approach is that it would not give the ability to precisely choose the book to navigate to (e.g. on a particular day you may wish to read from book 2, then from book 5, then from book 3, then from book 1, then from book 4).

What do you think? I know that something like this would be very useful for my daily workflow, and the point of it is to make the reading experience more seamless, easy, and enjoyable. However, I do not know what other Lute users would like.

Thank you for your excellent software. The result of your work is helping me a lot.

Edit (25 February 2025):
I think I should correct my thinking a bit. Since the point of this feature is to increase the user's convenience by providing a rapid way of moving to the next book and to the previous book, it may be unnecessary to add buttons to the hamburger menu. Needing to open the hamburger menu, then find those buttons, and then click on one of them would take too much time and effort and may not differ much from going all the way back to the Home screen in order to find the desired book. The way to let the user have immediate access to the next book and to the previous book would probably be to add those two buttons to the main part of the reading screen itself, but that may clutter the user interface. As a first pass, it may be more efficient to just add those two features as hotkeys. Anyway, I think the idea has now been expressed in full. I hope that it will be useful to you.

@Inquisitor-Ignotorum Inquisitor-Ignotorum changed the title Request: Ability to navigate to the next book and to the previous book from the reading screen While in the reading screen, navigate to the next book and to the previous book Mar 9, 2025
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

1 participant