search

Kevinjil / Jellyfin.Xtream

The Jellyfin.Xtream plugin can be used to integrate the content provided by an Xtream-compatible API in your Jellyfin instance.
GNU General Public License v3.0
90 stars 6 forks source link

Optimise TV overrides (Channel Sorting view) #91

Open sunnyd24 opened 3 months ago

sunnyd24 commented 3 months ago

Great plugin, thanks for your efforts! @Kevinjil

One issue I have observed is once channels are selected from "Live TV" tab, the list spans 10+ pages and has multiple number 1 channels from different categories at the top of list under "TV overrides" tab. This continues with number 2 channels and so on.......... in full list. So a sport channel numbered 1 could be next to an entertainment channel numbered 1, which is next to a music channel numbered 1.

So the need for manual channel sorting is required. It is a very manual process and as list could span 10+ pages, it would be good to optimise the experience through (all or some of the suggestions from below):

  1. Allow dynamic numbering, so that it re-sorts whole list as you enter a "number". (Currently it is hard to remember which number has been edited and which has not when scrolling through multiple pages)
  2. Manual sort by "Name" column or "Number" column (Makes similar named channels next to each other for easier manual numbering)
  3. Option to allow automatic Category sorting, so that all channels from same category are bunched together. e.g. channels 1-10 from entertainment, 1-10 from sports, 1-10 from music, etc.. (This would avoid them from mixing all into a random list, e.g. 1 sports, 1 entertainment, 1 music, all next to each other from different categories)
  4. Export list to be edited in a spreadsheet, and Import re-numbered list back into plugin. (It might me easier than using the Jellyfin plugin interface to make changes)

Thanks for you consideration.

Kevinjil commented 3 months ago

Thanks for the suggestions! I'll put this on-hold for now, mainly due to personal time constraints. Some of these were planned for after the implementation of #89 (searching / filtering in the front-end using the indexed database in the back-end).