[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Code Assist for CDT 3.0
|
I'm figuring out what to do with the engine. I will look at moving most of
the logic dealing with parse information into the completion node itself.
However sooner or later we need to create a set of completion proposals
which is a UI element, so this needs to be managed carefully.
Doug Schaefer
Ottawa Lab, IBM Rational Software Division
"Alain Magloire" <alain@xxxxxxx>
Sent by: cdt-dev-admin@xxxxxxxxxxx
02/16/2005 11:32 PM
Please respond to
cdt-dev
To
cdt-dev@xxxxxxxxxxx
cc
Subject
Re: [cdt-dev] Code Assist for CDT 3.0
>
> Hey gang,
>
> As a late entry into the plan, I will be working on porting the
Completion
> Processor over to the new DOM. We see a huge potential to improve the
> performance of this feature with the new DOM architecture, i.e.
separation
> of syntactic and semantic processing and the laziness of the semantic
> processing. I will also be looking to take advantage of the information
in
> the index more often than we do now.
>
> I will update the plan accordingly and provide documentation of what I
> plan in the next day or so. If you are also planning work in this area,
> please let me know so we can coordinate.
>
Very cool !
The UI CCompletionProcessor(IContentAssistProcessor) class merges
proposals coming from:
- code assist(AST:Source parser)
- extension point(Help contribution)
- code templates
The engine using the AST to provide the proposals,
IASTCompletionNode CompleteEngine.complete(IWorkingCopy
sourceUnit, int completionOffset)
is in the UI plugin. Is it possible for the future to move this engine in
the Core plugin?
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cdt-dev
