QuickSearch eXtended

[Samuel]

Yes but I can see the timeline of inserts changes etc...

[Boofo]

Actually, I like "QuickSearch Plus". It says it all.

[m^2]

"QuickSearch Plus" is in use already.

[Samuel]

You are right:
http://www.ghisler.ch/board/viewtopic.php?t=16451

This gets better and better. I never thought of so much posts just for one rename procedure.

Perhaps I should ask random.org

[Boofo]

How about QSFilter Plus?

[vic2009]

What do you think:
QuickSearch or QuickFilter?

I prefer "QuickSearch".
Your plugin is an improvement of TC quick search, not just about quick search filter. It works very well without quick search filter enabled.

Edit:
"QuickSearch Pro" sounds cool to me.

[Samuel]

For myself I also prefer Quicksearch now. Just a little bit of overthinking my decision brought me there.

Could everyone vote again in the first poll?
I reset the vote because I dont want to use a name that is already in use. (Almost everyone voted for "QuickSearch Plus")

Then I could stay at Google like QS.

Sorry for inconvenience.

[Boofo]

Actually, I like "QuickSearch++" better. Makes it stand out more. I voted for "QuickSearch Plus" but didn't see the other until after I voted.

[SQUIRE]

For myself I also prefer Quicksearch now.

The possibilities are endless:

[1] Beyond QuickSearch

[2] QuickSearch Unleashed

[3] QuickSearch Continued

[4] Essential QuickSearch

[5] QuickSearch Special

[6] QuickSearch Fx

[7] QuickSearch Rx

(I'm fighting the urge to put in something rude now! )

[8] QuickSearch Turbo

[theosdikaios]

I tend to
Total QuickSearch
SAM QuickSearch SAM stands for "Superior Algorithm Machine".

[Boofo]

Suckup!

[gmb]

I really like your addon, but NHF I don't like name "Google like QuickSearch".
For me, Google means "sorting by relevancy/quality" and that's something this addon can't do.
Better name would be "Stupidoldsearchenginesfrom90sbeforegoogle Like QuickSearch" but unfortunately it is to long

Before Google, search engines used to search and list web sites/pages with requested word in title and sorted them alphabetically.
Google was something completely different. Google searched web pages by content, and listed them by quality.

I don't know what "Google like" means to you, but for me, your addon is "Opposite-of-Google like"

What about "GL QuickSearch"?
Those who like name "Google like..." will know what that means. Those who don't like it, will ignore meaning of GL

Example: former CrapCleaner is now CCleaner...

[Samuel]

As it looks the tool will be named: "QuickSearch eXtended" in future. I like the name.

Ok back from the name issue to the program.
Sorting by relevance would be a nice addition:

2Christian: The dll could just return numbers for the files. (every int should be available for relevance)
3 if they match very little
2 if they match better
1 if they match best
0 if they should not be in list
This would be great. Christian please.

Could be used for
- higher relevance for "match beginning"
- different relevance for different levenshtein distances
- higher relevance for finding the terms in name and not in wdx data
- etc, etc

Edit:
I forgot that:
TC should also group the matches of same relevance. Starting with the top relevances.

On second thought I dont know it this is necessary for Quicksearch. What do you think?

[Nigurrath]

Hi,
I have a problem and possibly a request.
if the plugin is configured to also use some wdx extensions, it terribly slow down the quick search in the view of the file extension plugins (in the my network places), and when connected to an ftp site.

If you configured it to use some wdx (3 very fast indeed) extensions and go to the my network places or to an ftp site, and use quick search, TC hangs for around two minutes or more trying to find all the information from the wdx for the remote files (ftp) or for the plugins (which are not real files).

So the request is if it is possible to modify the plugin so it disable the wdx extensions search for some special folders (like the network places) and add to the ini file a list of exclusions by-category (like for example do not search into wdx for all the ftp connections or for some network paths).

Another interesting addition would be to limit the execution time to a maximum configurable value, as for the sockets, after which the search is terminated and TC returns responsive.


thanks

[Samuel]

Good ideas.

As a workaround use all wdx in the second wdx group:
wdx_groups=|1,2,3

So you could explicit activate the quicksearch in wdx by writing the "wdx_separator_char" once, and append the search text.

There are several problems using a wdx_timeout.
1) The timeout is not for a search process but for each individual file. (TC doesnt tell when a search ends. It just calls "MatchFileW" again and again)
2) There could be problems when terminating the computation of "ContentGetValue". Because some plugins may get into an invalid state. (The only official way to interrupt it would be available if the plugin supports "ContentStopGetValue", but I think most of the plugins doesnt support it.)
3) Until now I have limited process programming skills.