Very flexible idea for implementing AND, OR, NOT in autoplay
Posted: Wed Sep 07, 2005 6:09 am
I have read already several times that people want to have operators like AND and OR for building up there autoplaylists. I'm missing that, too.
I have a suggestion. For optimal flexibility you could solve this with nested playlists. Example of how it could work:
* You build an (auto)playlist A
* You build an (auto)playlist B
* You build a playlist X with option AND (this option thing would be new)
* You put A and B below X
AND would mean: All songs that are in A AND B (= intersection)
OR would mean: All songs that are in A OR B (= union)
This can be nested over several levels to build more complex criteria. AND and OR nodes can also carry several lists below (not only 2). And to make it perfect we could have a NOT node/playlist.
This feature would be extremely powerful and quite easy for users to handle!
I have a suggestion. For optimal flexibility you could solve this with nested playlists. Example of how it could work:
* You build an (auto)playlist A
* You build an (auto)playlist B
* You build a playlist X with option AND (this option thing would be new)
* You put A and B below X
AND would mean: All songs that are in A AND B (= intersection)
OR would mean: All songs that are in A OR B (= union)
This can be nested over several levels to build more complex criteria. AND and OR nodes can also carry several lists below (not only 2). And to make it perfect we could have a NOT node/playlist.
This feature would be extremely powerful and quite easy for users to handle!