Sorting list disambiguation/changes.

[ty5e3a45]

Feature request.

Hey, Currently, the Sort By drop-down on the index gives the following as options:

• Uploaded (Oldest First)
• Uploaded (Newest First)
• Seeders (High to Low)
• Leechers (High to Low)

Would you consider changing the options and behavior of the drop-down?

1. Having two options named "Uploaded" (even if specified) is un-intuitive and confusing.
2. Sorting by Seeders/Leechers is possible, but only by highest to lowest, not lowest to highest.
3. It is not currently possible to sort alphabetically, by size, or by uploader.

How about:

• In the table layout, add the possibility to click on "Name", "Size", "Date", "Uploader", "Seeders", and "Leechers" titles, which would sort torrents in ascending order based on the click value, and upon a second click would sort them in descending order.
• In the sort by box, have the options "Name", "Size", "Date", "Uploader", "Seeders", and "Leechers" listed, which when clicked, lists the torrents in ascending order based on the click value, and upon a second click, would sort them in descending order. This can be visually represented by a change in button color, or an arrow appearing next to the button indicating "up" for descending, and "down" for ascending. This way, if on the default layout, it is still possible to sort.

Thanks,

[josecelano]

Hi @ty5e3a45, I think we need those improvements. Regarding the sorting filter, it would be nice to select the field and the sorting order (ASC or DESC) or, as you've proposed, a second click to change the order from the current one to the opposite.

To implement all the UX improvements in this issue or others, I think we could need to:

• Improve the search "engine". Now, it's only a bunch of disorganized SQL queries. It's already tricky to add more changes. We would like to create a read model (maybe with a database optimised for searching like Redis or any other NoSQL). Otherwise, this part of the code will become unmanageable. Maybe we just need to clean a little bit the way we build queries or we only need to create new tables for searching, I don't know yet. We can also try to add these features first, but I have the feeling that is not going to be easy.
• Review the whole app interface from the UX point of view, including all the new features we want to add.

But let's see, maybe we can just try to implement these small changes with the current interface and code and get more feedback before implemente a big change.