[MonoDevelop] Navigate to dialog item filter
ibboard at gmail.com
Mon Aug 2 14:39:49 EDT 2010
On 02/08/10 19:31, Michael Hutchinson wrote:
> On Mon, Aug 2, 2010 at 10:41 AM, Lluis Sanchez Gual
> <slluis.devel at gmail.com> wrote:
>>> The new matcher matches "AbCdEf" when a filter "bC" is given. And it
>>> matches "DatabaseObject" when "DOB" is given - the latter may match (I
>>> don't think it should - upper case should always force a word jump
>>> IMHO) - but the bug report was about
>>> "DatabaseObject" vs. "DatabaseObjectBase" - in that case
>>> "DatabaseObjectBase" should be selected (however with "dob", "Dob" or
>>> "DOb" the "DatabaseObject" is the better match).
>> When typing in lowercase, the algorithm should consider that any letter
>> can potentially be a word start. Also, short matches should have
>> priority over longer matches. So 'dob' should match 'DatabaseObject'.
>> I'm OK about interpreting upper case letters as a forced word start,
>> although I never use that. If I want to look for DatabaseObjectBase it
>> is faster to type 'doba' than 'DOB'.
> FWIW, I always uppercase my acronyms and word boundaries, so I'd like
> my search to be faster :)
FWIW, I am *way* more likely to type a block of text than acronyms,
since I'm already thinking of the word. It's like text/leet speak: why
take the time to think "'you' so I want the letter 'u', 'are' so I want
the letter 'r', then a space, 'great' so I want 'gr' followed by '8'"
when you could (with a keyboard) just think "you are great, therefore I
need to type 'you are great'"? From that PoV, I'd much rather have
longer matches have a higher weighting unless anyone can show me any
cases where it obviously works against me.
I agree that fast searches are good, though :)
More information about the Monodevelop-list