aMule Forum
English => Feature requests => Topic started by: sparky23882 on January 07, 2006, 01:47:36 PM
-
Hello there!
I've switched from mlMac to aMule and I'm missing the filtering of search results. aMule does very basic filtering and you always have to hit "filter results" to get the filtered search results. mlMac filters as-you-type AND you can set filters like "-mp3 -wav hello" meaning there will be no files with "mp3" or "wav" in their names, but "hello" will be in every search result. It's not hard to do this, some minutes of work I guess, as there already is a filter (which unfortunately is not a good one) which should get fixed.
greetz,
Sparky
-
i already asked for this some time ago, but there was a technical issue.
here is the thread http://forum.amule.org/thread.php?threadid=6910&sid= (http://forum.amule.org/thread.php?threadid=6910&sid=)
-
Basic filtering? Do you know regexps?
-
Are regexps supported?
Where can I find the documentation about it?
I do know regexps...
-
You can use regexps on the filter field.
In adition for that, oyu can use boolean queries on search string itself.
Like
Linux NOT mandriva
or
linux NOT (mandriva OR ubuntu OR gentoo)
AND operator is also suported, and this applies also to extensions (like porn NOT wmv)
-
Ok and what characters enclose the regexp here?
// or "" or something else?
-
See http://www.wxwidgets.org/manuals/2.6.2/wx_wxresyn.html
-
Okay, so regexp are supported.
But I guess I'm too stupid to write a "search for string1 and not string 2".
(rar|iso) searches for rar and iso files, as (rar|iso). does (one or more occurrence)
(test){0}(.){1,}(rar|iso) _should_ search for rar or iso, but not for "test". But it doesn't.
Is there any document with some examples? This doesn't seem to be the regexps I
know from php... ease of use seems not to be the objective of this filter. Otherwise,
a simple "+" or "-" in front of a word would work...
-
Just so you know, sparky23882, hitting Return in the filter field acts like pressing the Filter button. It's a little more convenient that way.
On the other hand, I agree that regexp is a bunch of power that's not actually useful in the context of filtering searches, while a simpler, less powerful filter language might actually be more useful. No offense, Xaignar. :P
-
:(
-
Btw, if you want something more userfriendly, then you'll have to suggest alternatives, cause I'm pretty much blank.
-
Here is the (in my opinion) most user-friendly alternative to regexp filtering.
Very easy to do.
" " (space) = AND
" -" (space, minus) = NOT
Boolean searching. Case-insensitive.
"happy -mp3 -xxx" finds matches containing "happy" and not containing "mp3" or "xxx"
"fun -wmv -avi -mpg -mpeg -jpg" finds files containing "fun" while not being a image or video.
So you, for example, search for "deeds" (you want to find the new movie) and filter with something like this:
"-jpg -txt -html -(old date)" etc. The old date you'll see in the search results, the old movie will be there too, I guess.
Search-as-you-type would be terrific here, because you immediately see how search results get less and more precise.
It's fast, ist's very easy to use and a boolean "AND" and "NOT" is quite simple to do, I guess. And because there are no regexps that have to be correct, search-as-you-type woulnd't be a big problem, too. onChange of the input field's data, a new search os done within the search results.
Need more ideas?
-
Well, I'd argue for using " and ' as the delimitors for joined words. I.E. -"old date" rather than -(old date), since this is similar to what one is used to from search engines. But otherwise I agree. A way to specify regexps would also be nice, but that can wait (maybe >>regex<< or something).