Re: Issue 1444 in quodlibet: Add separate global filter for song collections

[quod...@googlecode.com]

Updates:
Summary: Add separate global filter for song collections
Status: Open

Comment #3 on issue 1444 by reiter.c...@gmail.com: Add separate global
filter for song collections
https://code.google.com/p/quodlibet/issues/detail?id=1444

We'd need a separate (optional) global filter for collections to make this
work.
But I'm not sure if this warrants the added complexity.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[quod...@googlecode.com]

Comment #4 on issue 1444 by halluc...@gmail.com: Add separate global filter

for song collections
https://code.google.com/p/quodlibet/issues/detail?id=1444

Hello, more information about such feature follows:

A user has a large collection, let's say 1000 albums.
The user undergoes a listening of his albums for many months. He always
uses the search bar to pick them.
At some point in time the state of the average album playcounts becomes
uneven. Some albums were listened once, some three times or more.
The user decides to give more of his attention to the less listened albums.
And he wants to use the search bar to pick them arbitrarily. Since the
collection is large, this excursion may take months.

Here an inconvenience emerges: the user has to prepend (type)
&(#(playcount:avg<3),...) to search his albums. Every day, every search for
possibly many weeks or months.

Now a solution is to add a partially saved search '&(#(playcount:avg<3),'
and choose it every time before typing a custom search.

However this is not the same as global exclusion pattern. Everything what
follows has to be named by a
tag, '&(#(playcount:avg<3),albumartist=tobin)', instead
of ''&(#(playcount:avg<3),tobin)'.

Maybe a plugin can provide a form of a double search. Let's call the global
exclusion pattern exclusion_1, the database database_1, the custom search
search_1. I'm not a programmer, so I can't judge the viability of this
solution. Normally QL performs search_1 on database_1. What the plugin
would do is to perform two searches. Perform exclusion_1 search on
database_1, and then again search_1 on database_1_after_exclusion.
Preferably, the global search pattern would be defined in the same window
as saved searches.