Keeping Old Tvheadend Web GUI

user_xy-79

This post is a friendly plea to not completely remove the old GUI, as it has sadly been announced. I can well imagine that you don't want to maintain both GUIs and therefore want to remove the old one, but you could, in return, keep the old one but no longer offer support or bug fixing for it.

Personally, I don't like the new GUI. The reason is that I find the old GUI much more intuitive to use, in the way how I often use the old GUI. I would therefore be happy if the old GUI could continue to be used as a fallback, as it is currently offered.

Please reconsider the complete removal of the old GUI and continue to offer a solution for users who don't want to or can't use the new one. For me, completely removing the old GUI feels forced, as if one is being compelled to use the new GUI whether one wants to or not.

If there are other users feel the same way, please leave a comment to let the Dev´s know.

DeltaMikeCharlie

user_xy-79 Personally, I don't like the new GUI. The reason is that I find the old GUI much more intuitive to use,

Are you able to expand on what areas of the New UI you find unintuitive? Perhaps you could compare and contrast with the Old UI to illustrate your point.

To be clear, this probably won't result in the Old UI being retained. However, if you think that the New UI can be improved in some way, the developers need to know.

chewitt

Unfortunately the Classic interface depends on obsolete JavaScript libraries that are riddled with security issues so there is simply no scenario where these can remain in our codebase, no matter how many users ask nicely (or otherwise) to keep the Classic interface around.

Two key points: a) Nobody will be forced to update their Tvheadend installation so if you prefer the Classic interface you can simply remain on a Tvheadend release that provides it, and b) Constructive feedback on the new Web GUI is welcomed.

Chris G

chewitt Constructive feedback on the new Web GUI is welcomed

Right here or somewhere else?

Ronny Bachmann

I'm also currently switching back to the old GUI all the time. For example, if I want to set a timer, I can just enter a keyword under "title" there. It then immediately lists all programmes that have that keyword in the title, including the start time and duration. Unfortunately, I haven't found the duration info in the new GUI yet.

oliver

Thanks for describing this so concretely — “switching back to the old GUI” for a specific workflow is exactly the feedback we need, and I’d like to close this gap properly.

To make sure I fix the right thing, may I ask where you were searching in the new GUI? There are a few places that behave differently at the moment:

the EPG → Table view, where the toolbar has a title search and the result list should already show a Duration column (along with start time) — plus a “Create AutoRec” button that turns the current search into a recording rule;
the quick search (magnifier / Ctrl-K), which currently lists matches with start time but no duration — if this is where you searched, that’s a real omission;
the Timeline/Magazine views, which have no search box at all yet.

If you can tell me which of these you used (or a screenshot of where you expected the duration), I’ll make sure the duration shows up there. And if the Table view’s search + Duration column happens to already cover your timer workflow, I’d still like to know — because then the problem is that it was too hard to find, which is worth fixing too.

Ronny Bachmann

oliver
Here is my workflow this morning in the old GUI:

Enter search term
Since the channel Arte doesn't have the current day's EPG available, click on the TV icon and leave the stream open for a moment, then close it again
Click on the extra text and create a recording timer

For private channels, the runtime of the program is important to me, as I don't like filling up the hard drive with commercials.

In the new GUI, I'm not really sure what the simple procedure looks like here.

chewitt

Chris G Right here or somewhere else?

Anywhere is good and mods will ensure the relevant staff see the post, but if you plan to give lengthy feedback or pick a specific topic it might be good to start your own thread.

martine

The Classic GUI issue makes sense especially for workflows like timer creation where the old interface is just quicker to get through. But its outdated JavaScript dependencies raise security concerns, making it difficult to justify keeping it in the codebase. I would focus the feedback on specific workflow gaps in the new GUI (e.g. missing duration in quick search), as these are tangible problems the devs can actually fix.

DeltaMikeCharlie

In the 'Table' view, you can type in some search text and the list will be narrowed. There is a duration column.

From there you can select the event to be recorded:

The main problem I see is that in the 'Table' view, there is no visual indication that the event has been scheduled for recording like there is in the 'Timeline' and 'Magazine' views.

Have I missed something?

Have you selected the 'Duration' column to display in the 'Table' view?