Re: date on search results (super)

This is just one more reason why the 'search' box (better titled the 'Find' box) should (if there is more than one matching result found) just turn into a Super Search for titles containing the listed words.

Among the other reasons:

Extra information besides date would be shown
New nodes would be shown first instead of last
Searches that match a ton of nodes are handled better:
- We don't immediately waste resources searching for a huge list of matches
- So you can see the first many matches more quickly
- If you want to see even more matches, you can just click "Next"
- You can instead tell the search to start over with oldest nodes first
- You get information about how much of the database was searched so far to find these matches
If the server is unusually busy, Super Search notices and uses even less of the server resources
We can concentrate on adding features to just one 'search' implementation (such as clustering hits from the same thread)
You can immediately customize the search in lots ways and try again
Two words: amoritized depreciation!

And I probably forgot a few.

- tye

Comment on Re: date on search results (super)

Replies are listed 'Best First'.
Re^2: date on search results (super) by jdporter (Paladin) on Dec 05, 2008 at 22:08 UTC
Well, it's gonna take a god to do that, or I'd have taken a whack at the patch myself. Look at Everything/HTML.pm, in `sub nodeName`, and replace code from line 934 through the end of sub. You'll want to load up some CGI params expected by Super Search into the `$q` object, i.e. `$q->param( HIT => $node ); # HIT = title; $node is the search stri +ng displayPage( getNodeById( 3989 ) ); # transfer to SS` [download] One question is whether you'd want the SuperSearch to execute and display some results immediately, or just load up the search form and wait for the user to submit. I'd vote for the former, personally. Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.	[reply] [d/l] [select]
Re^3: date on search results (super) by tye (Sage) on Dec 05, 2008 at 22:22 UTC
It always takes one of the gods to apply a patch. The fact that in this case the patch isn't as convenient for gods to apply doesn't actually prevent pmdev from producing a patch (which will not be a patch). (If I had recently seen a patch that had been tested on the pmdev test server, then I might further consider that difference, but I haven't.) Yes, I think the search should immediately run in this case. Most title searches will finish with a single submit of Super Search and the resulting server load will still be less than that generated by the current search behavior. Thanks for the pointers already provided. Thanks in advance if you produce something more concrete as well. I'm quite low on spare time but that usually changes at some point this month, so I might get around to updating Everything/HTML.pm with or without a more concrete patch then. - tye	[reply]
Re^4: date on search results (super) by jdporter (Paladin) on Dec 08, 2008 at 16:11 UTC
Thanks, tye. In case it helps, convenience-wise, I created a "patch" against Everything/HTML.pm via request for new code node - (patch). It should be good to go. I'd try to test it on the dev server, but I don't know how.	[reply]