[web] feature requests

[whatdoineed2do]

Suggestions for adding to web UI

• ability to update track ratings
  server has endpoint for updating track ratings that can be triggered from web ui using:

  library_track_set_rating (trackId, rating) {
    return axios.put('/api/library/tracks/' + trackId, undefined, { params: { rating: rating } }).then((response) => {
      store.dispatch('add_notification', { text: rating === 0 ? 'Track Rating Reset' : 'Track Rating Updated', type: rating === 0 ? 'success' : 'info', timeout: 1500 })
      return Promise.resolve(response)
    })
  }

using: vue-star-rating
UI: ModalDialogTrack and PageNowPlaying

• add to Q avoid duplicate tracks
  toggle functionality: when adding tracks to (a long) play queue (particularly play next), i do not want to duplicates track- entries - when a track is added to Q position, any previous instances of same track(s) should be removed to avoid duplicate

• files listing needs to be more user friendly
  Currently listing is grouped in directories , playlists and the files. If you want to view files in a large library you have to scroll a long way. Need to provide an index like scheme, similar for albums view

Need index to accomodate for different groups (file vs directory) have the same index. Possibly provide a different view per group (ie show all dirs or all files or all playlists etc)

• queue re-ordering needs more visual clues
  on IOS if you edit and drag an item in the Q there are no visial clues for where the track is being dragged: an sample impl is using "ghost" item option as:
  https://github.com/whatdoineed2do/forked-daapd/blob/6a1b8035402b93a4c87dfa33d75b95c9a3b6536f/web-src.v3/src/pages/PageQueue.vue#L63-66

[hacketiwack]

@whatdoineed2do, I was indeed wondering where the rating was coming from. Looking at your proposition, makes sense actually.

[whatdoineed2do]

IIRC, the track ratings can be autocalculated i believed based on number of times played, skippped etc - something similar to mpd and you can control it via the config file rating_updates flag. I wanted more control by setting the rating myself.

I never managed to submit a PR for this - in a sample impl, i have it dispalyed and settable on the track modal and now playing

      <star-rating v-model:rating="rating"
          :star-size="17"
          :padding="5"
          :show-rating="false"
          :max-rating="5"
          :increment="1"
          :inline="true"
          :clearable="true"
          :active-on-click="true"
          @update:rating="rate_track">
        </star-rating>

where rate_track calls library_track_set_rating . My impl or the star library has a bug on display of stars after the initial assignment of the rating which i never solved but the above may give you an (partially) working example

[hacketiwack]

FYI, with this commit, a breadcrumb has been implemented to simplify the navigation within directories (Files).

Moreover, there is still no index implemented. The main problem for this is to have something visually and from a user experience point of view acceptable. Any mockup for such a view can be proposed.

Not directly related, and for the record, I don't have such difficulty with my library, because I tagged all my files (with MusicBrainz Picard) and named them automatically following a scheme that avoid name clashes (e.g., two releases of the same album having the same name but different track count).

This name scheme uses MusicBrainz identifiers:

/first-character-of-album-identifier/second-character-of-album-identifier/album-identifier/track-identifier

Concretely

Music/7/4/7405a38a-a72e-4559-916a-26ff00ed2b93/30ad4c32-1fab-3536-8b7c-fb1d32207221.mp3