Skip to content

Search through library should use backend side implementation #124

Open
@orontee

Description

@orontee

With current implementation, search happens locally in the currently visited directory.

See https://docs.mopidy.com/en/latest/api/core/#mopidy.core.LibraryController.search

  • Add a model class for artists
    Since search results may contain albums, artists or tracks.
  • Add a library search action and extend model with search results
  • The search should be performed in a task and must be cancelable
  • UI to display search results
  • Setting to customize search query

UI draft

Displayed when entering search mode (by clicking search button or corresponding shortcut).
Page made of stack widget with:

  • A page made of a single centered label for "no result to display so far".
  • A page made of a progress bar for "ongoing search" (with a cancel button?)
  • A page for results with three sections albums, artists and tracks
  • Clicking on an album should enter the corresponding library view
  • Clicking on a track should enqueue/play (?) that track
  • Clicking on an artist should enter an artist view
  • Access to all album or tracks results

Questions left opened / Remarks

The interest of using the backend side search implementation is very limited when using Mopidy-Local, see
mopidy/mopidy-local#16.

How-to search locally in currently visited directory?

How-to disable some Mopidy backends? Should we care?

How-to choose search criteria? Should we care?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions