[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: [Controversial Patch for Bug 18180] kfind sloppy match for simple search strings
From:       Kurt Granroth <granroth () kde ! org>
Date:       2002-07-19 16:27:30
[Download RAW message or body]

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.

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.

Just some ideas.
-- 
Kurt Granroth - "KDE -- Conquer Your Desktop"
KDE Developer/Evangelist | granroth@kde.org
http://www.granroth.org  | kurt@granroth.org

[prev in list] [next in list] [prev in thread] [next in thread]