>Maybe it would be a good idea to be able to define a SQL for the
>enumeration besides just the type ?
>This would make it possible to limit the selection list, for example
>just showing all playlists that contains tracks with a specific genre
>or something. In the playlist example this is probably not so useful,
>but it might be useful in other situations.
>
I'm not sure I understand what you mean exactly.
I think most of my dynamic parameterised playlists would feature just one
param. Other filtering would be within the SQL. Eg "Play random electronic
music from {year}" would only require a quick selection of the required year.
I think something like "Play random {genre} music from {year}" may be nice, but
fiddly from the remote control.
"Play random electronic music between {year} and {year}" may be useful.
Instead of having to select two years though, I would probably write a query
like "Play random electronic music around {year}", and calculate a range of
years within the SQL (eg. +/- 5 years from the selected year).
Multiple selections could be viable, I guess, so {multiple years} could allow
selection of several years, which could be passed as a comma separated list in
one single parameter which would be used in a "WHERE xxx IN @param" expression.
Did you mean that the selection list would be filtered based on some info
within the SQL query? eg. in my "Play random electronic music from {year}"
example, you could filter the selectable years to be only years that contain
tracks with the electronic genre? That may be nice, but not necessary.
Phil
_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/plugins
