wiki:WebFrontendWishlist

Version 9 (modified by Karl Egly, 11 years ago) (diff)

--

Last updated 17th Jan 2014

This is the Developer wishlist for the WebFrontend?.

Please sign each item you add "(Added by StuartM)", and if you want to work on something then add "(Accepted by StuartM)".

Small Tweaks or Minor Features

List anything relatively easy/minor to add here:

  • Make guide time bar static so that it's visible even when scrolling down the page (Added by JimStichnoth?)
  • Make it easy to edit title/episode title of recordings, then re-run the metadata grabber (Added by dekarl)
  • Display the names of all matching channels, or "any", on recording rules depending on the "this channel" filter. (Added by dekarl)
  • Mark recording rules that refer to deleted channels as broken. Mark them as "warning" unless they have the "this channel" filter enabled, then mark them as "error, needs attention". (Added by dekarl)
  • Make it easy to see past / future recordings per recording rule. (Added by dekarl)
  • Allow ordering of recording rules by "next recording date" in addition to "last recording date". (Added by dekarl)

Big Features

List the big ticket stuff here, anything that requires more than a few minutes of work:

  • One click HTTP Streaming of recordings (Added by StuartM)
  • One click starting playback (or adding at the end of the playlist) on a frontend (Added by dekarl)
  • Toggle auto-expire on recordings (Added by StuartM)
  • Websocket support in http server (Added by StuartM) (Accepted by DBlain)
  • SSL support in http server (Added by StuartM) (Accepted by DBlain)
  • Playlist editor for recordings in the frontend's web frontend (Added by dekarl)

Stuff to make mythtv-setup redundant

Ability to

  • configure the database connection and initialize the DB Schema (Added by StuartA)
    • We can't create and initialize the schema without root access to the database server, which is why mythtv-setup never handled this task either, but required the user to do it independently with the mc.xml file. This was one of the reasons for wanting to move to an embedded database. We could ask the user for root credentials temporarily to take care of all that for them. (rwagner)
  • define capture cards (Added by StuartA)
  • define data sources (Added by StuartA)
  • initiate channel scanning (Added by StuartA)