[Controversial Patch for Bug 18180] kfind sloppy match for simple search strings

[Klas Kalass]

Am Friday 19 July 2002 18:27 schrieb Kurt Granroth:
> On Thursday 18 July 2002 10:28 pm, Klas Kalass wrote:
> > Example:
> > kfind -> kfind.cpp is FOUND
> > k?ind -> kfind.cpp is NOT FOUND
> > k?ind* -> kfind.cpp is FOUND
> > .c -> kfind.cpp is FOUND
> > *.c -> kfind.cpp is NOT FOUND
> >
> > May I apply?
>
> This is an intriquing idea.. but it's not at all obvious behavior.  I
> wonder if it would be better if the results were somehow split into two
> sets.. absolute matches and "kinda" matches.
I think I like that, but I am not quite sure how to implement this.

>
> That is, all matches that would happen in a traditional search would show
> up first.  The matches that were a bit fuzzy (like 'kfin' matching
> 'kfind.cpp') would show up in some other way.  Maybe a splitview or
> slightly greyed out or something.  Or maybe the traditional matches could
> be bold.
I do not like the idea of a splitview because it adds some kind of visual 
complexity. But giving the icons of "fuzzy matching" files a different look 
(semitransparent or whatever) and changing the backgroundcolor of listview 
entries (for kfinddialog as well) might be a good idea.
Ideally they would also be sorted at the end but I have no idea if this can be 
done for the konqueror part of kfind. 

Making the "traditional matches" bold has the problem that with some fonts 
bold and normal can not be distinguished very well. 
And people always having exact matches might send bug reports that the font is 
bold ;-)

Cheers,
Klas