Marvin Humphrey wrote on 3/17/10 11:04 AM:

> So, I think what we should do is clean up PhraseScorer so that it is clearer,
> then create ProximityScorer by cloning and modding it.  It's a mild violation
> of DRY, but that doesn't bother me.  All of us will benefit from the cleanup,
> and you'll walk away with a thorough understanding of the algorithm and a
> top-flight ProximityScorer.

ok. I'll go this route, creating a new KSx::Search::ProximityScorer. I'll send
some patches along when I have something useful.


-- 
Peter Karman  .  http://peknet.com/  .  [email protected]

Reply via email to