Separate displays for Music lib

[roeland]

For example amarok style. Artist / Album / Tracks Albums / Tracks Artists / Tracks

And many many more.

[daniel]

this involves restructuring the treeitem classes, so every type can be child of the other items.

change children collection from QList -> QHash or QMap should be done together with that.

this should also speed up library loading tremendously, might make xml caching for the library obsolete, which is kinda hard to support with configurable grouping anyway.

lets see :) will work on that as soon as we got 0.6 pushed out and idle support is merged into trunk

[daniel]

also add disk grouping possibilty as requested by a wish of roeland's father

how shall we handle albums that only got no disk tag provided? asume that it is disk one, put a disk node with text "<unknown>" there there, like it is with albums or just put the songs directly below the album node?

the last option would lead to a tree which has different depth, which should be no problem for the design i got in mind but might disturb the user experience. well, also putting "1" or "<unknown>" has that possibility :>

maybe matter of taste, we could provide an option for that but that seems a bit too much for me :>

[roeland]

If there is no disc info just put the songs directly below the album. Extra disc nodes only are usefull if we actually have multiple discs (or the disc is explicitly set).

Of course we then have the decision to make if an album only contains 1 disk but the user (explicitly int he id3tags) has set disc=1?

[daniel]

mhm, thats a bit tricky, also if there are some songs with disk, some without on the same album. I would say the cleanest way might be to do exactly what is in the tag without added intelligence. that way the user has full control over what happens through propper tagging.

if someone really requests it, we could add an option to convert an empty disk tag to 1 per default.

[roeland]

You are right. Users should fix the data :)

While you are at it migrating from QList -> QMap or QHash seems like a good idea.