refiining runners

[Aaron J. Seigo]

On Thursday 07 February 2008, Aaron J. Seigo wrote:
> can override. perhaps the priority rating should also be taken into
> consideration alongside relevance for final ranking in the UI?

chatting with ruphy on irc just now it occurred to me we have *another* metric 
that is being ignored in the rating calculation: exact, possible ("fuzzy") 
and informational.

perhaps all exact matches first, followed by all informational then all 
possible? i put possible last since those are likely to be the bulk.

that's 3 values to combine into one ranking thus far ... will have to play 
with this =)

ah, another thing is that many runners check and only do anything if there are 
3 or more letters in the search term. instead of running them only to come 
back, maybe we should allow runners to define some parameters that would 
short-curcuit their being run at all until they are met. this feels like a 
premature optimization at this point in time, but might be useful down the 
road...

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20080207/c6bb7572/attachment.pgp