My first experiences with the pro edition

I’ve indexed our entire code base which was a very easy task (very pleased in fact with how slick this was).

Now I’m onto playing with each type of search that can be performed. So far I’ve got little mixed impressions with “free format” searches. For example DataSet returns classes whose content contain the word DataSet – fine, that’s what I was expecting – but it also returns hits for classes whose content contain the words Data and Set. I would really only have expected this to happen if I had searched for Data+Set. This seems overly inclusive, resulting in hits where the majority are false positives. If this is indeed the expected behaviour then I think it seriously reduces the usefulness of the tool in practice.

Christian

Hey Christian, I am glad that our indexing work flow was satisfactory for you… but we have MANY cool ideas on how to make it even more slick!

Regarding your question about searching: we apply extended searches be default for terms that have mixed case. Camel Case and Pascal Case search terms are broken out into separate terms as well as a single term. For the example you have given, DataSet actually performs a search for “dataset” and “data” and “set”. To only search for DataSet simple put quotes around it.

For example (from koders.com):

http://www.koders.com/default.aspx?s=DataSet

returns 676,225 results

and

http://www.koders.com/default.aspx?s=%22DataSet%22

returns 9,980 results

Right, that search logic is kinda what I expected was happening. I think the the page that shows examples of the types of search needs improvement with two entries – one to indicate the Camel/Pascal case extended seach and another that shows a literal search (here’s the page I’m refering to: http://www.koders.com/).

It seems intutive to me that the ide plugin search modes should perform a literal search when in “Strict” mode, and to perform a Camel/Pascal extended search in “Broad” search mode.

Christian

Thanks for the feedback Christian, Dianna and I will add it to the feature list and hope to get that to you in the next release of the plugins.

Unrelated we are working on the examples so we will incorporate your feedback. Any other suggestions?

I suppose as a nice to have it could be useful when setting up projects to be indexed, to able to exclude specific subfolders. This could be useful for those projects that share code between multiple projects.

C

Alternatively, you could break a larger project down into smaller projects if that fits your needs.

You’re probably right.