[MonoDevelop] Navigate to dialog item filter
Lluis Sanchez Gual
slluis.devel at gmail.com
Mon Aug 2 06:24:38 EDT 2010
The old algorithm is a bit slower, but it gives better search results.
For example, try looking for 'ccommand'. The list you get using the old
algorithm makes much more sense to me than what you get in the new one.
Also, the new algorithm can't handle some queries. For example, if I try
to look for CustomCommandCollection using the strings 'comcoll',
'cuscoll' or even 'commandcollection' I don't get any result.
Those issues should be fixed before switching to the new algorithm.
El dg 01 de 08 de 2010 a les 18:21 +0200, en/na Mike Krüger va escriure:
> I changed the navigate to dialog item filter - I had it a few versions
> before - but then reverted it to the 'old' navigate to type/file filter.
> (nobody recognized afaik)
> But after that the navigate to dialog was very slow when filtering large
> projects like the monodevelop one - (but nobody recognized that too).
> Now I've changed it back to the completion filter - the code completion
> uses a very easy greedy algorithm - the navigate to filter was more
> complicated. (but I think it's more a matter of taste which one is more
> I attached a small test file which compares the speed of the two
> algorithms. Most of you know the filter from code completion - but I
> want some feedback from our users about that issue.
> I prefer the code completion filter alone for consistency reasons - I
> like how it behaves & how to search items with that. It should behave
> like the R# filter.
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.com
More information about the Monodevelop-list