Smarter filter bar with tag style text input (tag:xyz installed:yes...)

[CuddleBear92]

The Query field should be able to take on tags and creators or parts of the string.

If you don't want to free form it like typing just "big tits" you could prefix it with whatever the metadata is like "tag:big tits" or "creator:FOZ"

Free form without these constraints with full wildcard would make the most sense though.

Pressing enter in the query filter field should add whatever is in the field to the filter like in the "add filter" side panel. Just have it be filled with quick text by the user instead of that tiny dropdown menu. Listing the queries with new lines to remove it can still work though.

Note: see how Hydrus is querying its files, easy lines to add and add multiple AND prompts in seconds without navigation.

[Willy-JL]

Again with the “should”. Quit it.

But again, yes, the filters could use some work. I don’t know yet how I’m going to do it, but I do plan on improving them. This is a good option, we’ll see

[FaceCrap]

The query field already does take parts of a string. Also, duplicating what is already possible through the standard filter options is overkill, especially if you're querying for things which already can be used from the filter dropdown. Adding them to the filter dropdown is then not needed since they already exist as filter option with implied AND action. Why type if all you need to do is a couple of clicks? Now, if we're talking about extending the filter logic, choosing if a filter needs to be of type AND or type OR, that would make more sense to me. Since just about everything else can already be filtered through the dropdown. Comparing it to how other software does things... well, it's not a clone, so things are bound to be different.

[Willy-JL]

Plan in the long run is to completely change the filter system, because this one doesnt really cut it. i was thinking something along the lines for what github does for issues and prs, where you have a search box that can take special parameters like is:open or label:feature, but also normal text for pure string searching. Not sure how to implement it yet tho, so we'll see

[FaceCrap]

the current filter system life could be extended if it would support AND and OR logic, same for the inputbox (e.g. literal AND / OR or && / || operators) That would already extend the possibilities a lot.

[thelapdragon]

It would definitely be useful if we could stack filters - I'd like to be able to exclude multiple "type" filters, for example, without making a full inverse filter for each one.