@osmosis:
Agreed to bump this 
Quote:
|
Another thought I had was if your comparisons could contain more than one variable the query language itself would be exponentially more powerful. The current format is <field> <comparison> <value> but it would be better if your <value> could also be a "field" variable, such as "?FOLDER ends YEAR" and other cool ideas.
|
I also want to extend your suggestions that <field> could also be a string expression,
so that smart view will work with non-built-in-tags, too.
FLAC for example has a field named ORGANIZATION.
?(ORGANIZATION = "Touch Records") doesn't work,
as there is no variable (reference-address) assigned to this tag so far.
But creating query-variables for all possible and impossible tags/fields
won't be the real McCoy.
So how about this (using values)?
?('ORGANIZATION' = "Touch Records")
or, as function (using methods):
?(field("ORGANIZATION") = "Touch Records")
or, as attribute (using objects):
?(field.ORGANIZATION = "Touch Records")
Quote:
|
I'd like to add that HASALBUMART would also be extremely useful for query building, especially where Simple Album Art view is concerned (no blank llamas!).
|
INPLAYLIST would also be nice:
Check, if a file is in a playlist having this name.
Then, you could also compare playlists or play parts of them 
P.S.: How about an XOR operator?