Merge lp://qastaging/~mhaulo/mixxx/multilevel_crates_playlists into lp://qastaging/~mixxxdevelopers/mixxx/trunk

Hey Mika,

thanks for your great set of new features.

Although there's enough time until 1.11 comes out, here are my preliminary concerns.

1. Crates and playlists follow the concept "A crate can have one or many subcrates which in turn can have subcrates too." I am not sure about the semantics here. Some of our commercial competitors use the concept of folder and playlist: A folder can have subfolders and playlists. A playlist cannnot have subfolders nor subplaylists". I would be glad to hearing other opinions.

2. You've introduced schema version #14. It is not really compatible with version 3.
If one creates subcrates with your branch, older Mixxx versions are not able to display the tree. Instead all your subcrates are leaves below the sidebar item of "crates".

3. Please add a comment to CrateDAO::getCrates() and PlaylistDAO::getPlaylists(). They both return a QMap which is sorted by its key value. I forgot that when I helped you out :-)

Tobias

Hey Mika,

Thank you for your work!

Sorry for not including this in 1.11.

Here are some comments:

If I understand right, your concept turns Crates into virtual Folders, with files and sub-folders.
Each crate has exactly one parent crate.

I would prefer if a crate can be member of different parent crates.
This can be done for example by an additional table which stores the crates included in a parent crate.

I think We need also a duplication handling when deleting songs from a crate.
If you have the same track in crate "Rock" and in crate "Punk", you make "Rock" the parent of "Punk" and then delete it from "Rock" ...

Kind regards,

Daniel

Hi Daniel & the team

> If I understand right, your concept turns Crates into virtual Folders, with
> files and sub-folders.
> Each crate has exactly one parent crate.

> I would prefer if a crate can be member of different parent crates.
> This can be done for example by an additional table which stores the crates
> included in a parent crate.
>

If I remember correctly (it's been a while since the last time I've worked on Mixxx...), the virtual folder thing you described is how it works right now. But I agree with you that it doesn't make sense to restrict a crate to only have one parent crate.

I'm not exactly sure how much time I have available for this task in the near future, so if you're in a hurry with this one, please feel free to take over the task. Even though the changes you proposed (including duplication handling and any other stuff needed) don't sound like anything huge, I might need some extra time to set up a development environment and to recap where I left off almost two year ago :-)

Hi Mika,

Thank you for your comment.

It would be nice, if that can be part of 1.12.
But I have myself other tasks with a higher priority.

So I would be glad if you will find time later or someone else will pick up this task.

> Hi Mika,
>
> Thank you for your comment.
>
> It would be nice, if that can be part of 1.12.
> But I have myself other tasks with a higher priority.
>
> So I would be glad if you will find time later or someone else will pick up
> this task.

I will probably continue on this branch unless you complete it.