[UI Enhancement]: Search/home page view all button for a categories #601

Open
opened 2026-02-20 01:06:31 -05:00 by deekerman · 7 comments
Owner

Originally created by @Albuca on GitHub (Aug 21, 2022).

Describe the feature/enhancement

UI Enhancement:

When searching, the results are returned as a 1 high row, that allows for scrolling to the right if it overflows the webpage window.
Verses the library view, where the overflow creates a new line, and you can scroll down to see additional titles.

Personally I much prefer for additional rows and scrolling - makes more sense to me to use up all of the screen real-estate if it is there.

Cheers!

Originally created by @Albuca on GitHub (Aug 21, 2022). ### Describe the feature/enhancement UI Enhancement: When searching, the results are returned as a 1 high row, that allows for scrolling to the right if it overflows the webpage window. Verses the library view, where the overflow creates a new line, and you can scroll down to see additional titles. Personally I much prefer for additional rows and scrolling - makes more sense to me to use up all of the screen real-estate if it is there. Cheers!
Author
Owner

@advplyr commented on GitHub (Aug 21, 2022):

How would you handle the different categories in that case? Search results return series, authors, etc.

@advplyr commented on GitHub (Aug 21, 2022): How would you handle the different categories in that case? Search results return series, authors, etc.
Author
Owner

@Albuca commented on GitHub (Aug 22, 2022):

Good question... Personally I would be happy if the results cascaded and were separated by the series, title, author, etc headings. That is to say, list all of the results of each category (row by row), and when the category is complete - have a divider that would separate out the next category and it too would be displayed row by row.

Couple other ideas:

  • If it is only returning one category, use the whole page
  • Display the first row of results per category, and have a downwards facing arrow that could be clicked to then cascade out all of the results of that section row by row.
  • Make it an option. Search results how they are now, or fully cascaded and you would have to scroll to get to the category you want.
@Albuca commented on GitHub (Aug 22, 2022): Good question... Personally I would be happy if the results cascaded and were separated by the series, title, author, etc headings. That is to say, list all of the results of each category (row by row), and when the category is complete - have a divider that would separate out the next category and it too would be displayed row by row. Couple other ideas: - If it is only returning one category, use the whole page - Display the first row of results per category, and have a downwards facing arrow that could be clicked to then cascade out all of the results of that section row by row. - Make it an option. Search results how they are now, or fully cascaded and you would have to scroll to get to the category you want.
Author
Owner

@advplyr commented on GitHub (Aug 23, 2022):

I can't think of a good UI design that would have categories overflowing onto multiple shelves.

There is another request about the home page categories along the lines of adding a "View all" button that will show all the items in that category instead of the top 10. This could be the same for search because the search is also capping the number of results for each category. The view all button would direct you to another page that shows all the results.

What do you think?

@advplyr commented on GitHub (Aug 23, 2022): I can't think of a good UI design that would have categories overflowing onto multiple shelves. There is another request about the home page categories along the lines of adding a "View all" button that will show all the items in that category instead of the top 10. This could be the same for search because the search is also capping the number of results for each category. The view all button would direct you to another page that shows all the results. What do you think?
Author
Owner

@Albuca commented on GitHub (Aug 23, 2022):

That would be a much better implementation (the 'view all' button). It would allow you to keep the current easily visible split between result categories - and allow one to focus and expand on one particular category and see all of the results. Especially if the current results limit is set to 10. 


From: advplyr @.***>
Sent: Tuesday, August 23, 2022 15:24
To: advplyr/audiobookshelf
Cc: Albuca; Author
Subject: Re: [advplyr/audiobookshelf] [UI Enhancement]: Search Results Display as One Row (Issue #923)

I can't think of a good UI design that would have categories overflowing onto multiple shelves.
There is another request about the home page categories along the lines of adding a "View all" button that will show all the items in that category instead of the top 10. This could be the same for search because the search is also capping the number of results for each category. The view all button would direct you to another page that shows all the results.
What do you think?

Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@Albuca commented on GitHub (Aug 23, 2022): That would be a much better implementation (the 'view all' button). It would allow you to keep the current easily visible split between result categories - and allow one to focus and expand on one particular category and see all of the results. Especially if the current results limit is set to 10.  ________________________________ From: advplyr ***@***.***> Sent: Tuesday, August 23, 2022 15:24 To: advplyr/audiobookshelf Cc: Albuca; Author Subject: Re: [advplyr/audiobookshelf] [UI Enhancement]: Search Results Display as One Row (Issue #923) I can't think of a good UI design that would have categories overflowing onto multiple shelves. There is another request about the home page categories along the lines of adding a "View all" button that will show all the items in that category instead of the top 10. This could be the same for search because the search is also capping the number of results for each category. The view all button would direct you to another page that shows all the results. What do you think? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
Author
Owner

@advplyr commented on GitHub (Aug 23, 2022):

I'm going to combine this request with the one for the home page since they are both "categorized" shelves using the same component in the UI. Combined with #810

@advplyr commented on GitHub (Aug 23, 2022): I'm going to combine this request with the one for the home page since they are both "categorized" shelves using the same component in the UI. Combined with #810
Author
Owner

@Albuca commented on GitHub (Dec 15, 2022):

I noticed another issue, that actually makes this enhancement more of a solution to a potential bug.

When searching for something that a lot of my books have in common ( "2022" or "[" ) I only get ~12 results, even though there are many other books that meet the criteria. I get one "scroll" with the arrow on the right, and thats it - no other results are displayed.

@Albuca commented on GitHub (Dec 15, 2022): I noticed another issue, that actually makes this enhancement more of a solution to a potential bug. When searching for something that a lot of my books have in common ( "2022" or "[" ) I only get ~12 results, even though there are many other books that meet the criteria. I get one "scroll" with the arrow on the right, and thats it - no other results are displayed.
Author
Owner

@advplyr commented on GitHub (Dec 15, 2022):

It's not a bug it was just only designed to return a certain number of results for each category. That is why this enhancement will be useful.

@advplyr commented on GitHub (Dec 15, 2022): It's not a bug it was just only designed to return a certain number of results for each category. That is why this enhancement will be useful.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/audiobookshelf#601
No description provided.