Explore the feasibility to move all real models to a not UI thread. Replace the models in the UI by proxy models.
After that, try to have a generic view that can display both all albums and all artists views.
After that, try to have a generic view that can display both one album and all tracks views.
This is necessary to allow the user to customize the kind of views he has. That should allow to match the "Simple by default, powerful when needed".
While sitting bored in the train for a couple of hours I started working on implementing T6294 which requires some changes to the proxy filter models. I came up with a working solution, but I've seen you started working on this one here.
Since they may interfere, I'd like to know if it still worthwhile pursuing my solution.
The plan is:
-move all the model classes (e.g. allartistmodell.h/cpp, albummodel.h/cpp etc. and the albumfilterproxymodel) to a new subdirectory "models". This is just to structure the code a little bit.
-add dedicated proxy models in the new subdirectory for allartists and alltracks (maybe with a common base class), which implement an enqueue method that adds all filtered entrys to the playlist. This can also be used for sorting in the future.
-add the enqueue and replace and play buttons
What do you think?
I only added a couple roles in the existing models without any extra modifications. I have created a new grid view and delegate that should be able to display albums, artists and tracks. I am missing the open action at this time. I would like to do the same thing for a list view.
I have reused FilterBar and NavigationBar without any modifications.
There are two options:
What do you prefer ?
If the data models doesn't change, I can wait until the merge. I have to discuss with the VDG about the placement of the button anyways.