Code Assist and Search Engine restrictions (was Re: [cdt-dev] (no subjec

["Thomas Fletcher" <thomasf@xxxxxxx>]

Sorry for that folks, my original message and subject got cleared out.

The numbers that I mentioned were the "worst case, full header" 
configuration for the project.  The best case turned it from
500files/10min to 14000files/10min ... but it still took 10
minutes for my code completion to come back to me =;-)

I've submitted a patch and it looks like Bogdan's agreeed to vet it.

Thanks,
 Thomas


Douglas Schaefer <dschaefe@xxxxxxxxxx> said:

> 
> +1 
> 
> I think this would be appropriate for 1.2. Code assist is less dependent
> on search in 2.0. 
> 
> I don't mind getting different results at different times with code
> assist. Producing a partial list would be better than no list. 
> 
> Doug Schaefer, Senior Software Developer
> IBM Rational Software, Ottawa, Ontario, Canada 
> 
> 
> 
> "Thomas Fletcher" <thomasf@xxxxxxx> 
> Sent by: cdt-dev-admin@xxxxxxxxxxx 
> 
> 
> 02/12/2004 11:25 AM 
> 
> 
> Please respond to
> cdt-dev@xxxxxxxxxxx
> 
> 
> To
> <cdt-dev@xxxxxxxxxxx>, <cdt-ui@xxxxxxxxxxx> 
> 
> cc
> 
> Subject
> [cdt-dev] (no subject)
> 
> 	
> 
> 
> 
> 
> 
> 
> 
> 
> Folks,
> 
>  I mentioned about adding a timeout to the amount of time that 
> an operation should wait for the indexer.  I currently have 
> run across a very serious usability issue.  With the indexer
> fixes that Bogdan has put in, the indexer now reliably will no
> longer just "die" when there is some sort of fault.  This is
> great.
> 
>  The downside is that I've determined that a particular project
> I have will take ~5h to index (500 files/10min w/ 15,000 files 
> total).  If I hit Ctrl-Space to "code complete" then my system
> goes blocked until the indexer finishes.
> 
>  Obviously this isn't what we would like to have.  I would like
> to submit a patch for this, but there are a couple of approaches
> and I'm looking for advice on what would be most readily acceptable
> for the 1.2 branch.  What I'm proposing as a short/safe solution
> would be
> 
> - Adjust the SearchEngine to have an additional search() method
>  that would also take an option on how to deal with the indexer:
>  ICSearchConstants.FORCE_IMMEDIATE_SEARCH,
>  ICSearchConstants.CANCEL_IF_NOT_READY,
>  ICSearchConstants.WAIT_UNTIL_READY_TO_SEARCH
> - Adjust the CodeCompletion to use the FORCE_IMMEDIATE_SEARCH
>  for the 1.2 release to stop the indexing temporarily while
>  the completion proposals are searched out.
> 
> This would lead to "different results at different times", the
> other alternative would be to use the CANCEL_IF_NOT_READY and
> not show any results until we can show all of the results.
> 
> Thoughts and opinions,
> Thanks,
>   Thomas
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> 
> 



--