Comment 36 for bug 671632

My point of view:

1) We can just ignore by now that smart crates are filled automatically. I also think that in this discussion we can treat them like regular crates.

2) I agree, crates and playlists should only belong to one parent item. If you want the content of a crate to be showed to many other crates (like if you wanted to include all tracks "marked with a specific tag" in some crate) you can use smart crates.

3) If we let a crate contain tracks and other crates, how are we going to display all this? Obviously, on the browser tree only the subcrates would be visible. Shall we display the subcrates in the track list? How will we handle ordering for example?

If we use folders as the grouping entities, and we don't allow them to directly hold tracks we avoid this issues. We don't loose organizing power: you just have to put the "spare" tracks in a subfolder. Plus we can have the recursive view when the parent folder is selected. I think this is the best way to implement all these concepts..