Comment 34 for bug 671632

I think that purpose of folders/subcrates is basically the same. It is not to have infinite list of crates/playlist in which is hard to navigate, hard to name it. Now i have crates named in style Rock - 80's - slow. Flat structure makes me to have many crates starting with Rock, some starting with Rock - 80's... Navigation through this is not nice.

In the end it doesn't matter what is container for crates (folder/parent crate). The point seems to be reducing number of displayed crates at the moment and help navigate through hierarchy.

I see the possibility of crate being in more folders simultaneously as source of confusion. Example:
Three crates: Rock, Floorfillers, fast. Fast being in folders Rock and Floorfiller at the same time. This means if i add new fast rock song to Rock/Fast it will automaticaly become Floorfiller even though it can be floorkiller. If I need a song to be in more places in hierarchy i can put explicitly in all places i need.

I would treat smartcrates as regular crates. At least from users view.

I really like the idea of recursive crate view.

I'd like to start with adding possibility of crates containing other crates as it looks the most simple and useful starting point. The second step would be folders for playlists. Next one would be adding neat features like recursive views smartcrates, etc.