[Monodevelop-devel] Working on the monodevelop dom after 2.2
Lluis Sanchez Gual
lluis at novell.com
Mon Sep 28 11:45:06 EDT 2009
El ds 26 de 09 de 2009 a les 15:03 +0200, en/na Mike Krüger va escriure:
> > This is more or less what non-.NET languages have to do currently:
> > Munge some stuff into the DOM for 1), custom implementation for 2), 3)
> > [which is refactoring also, isn't it?] is basically impossible.
> > I'm on board with a unified, high-level DOM for populating
> > quickfinder, classpad, etc. [Zeroth bullet]
> > If this part is generalized enough to support native hierarchy
> > structures for various languages [currently missing], easily updatable
> > [currently exists], and easily and flexibly queryable from addin code
> > [currently missing], completion doesn't necessarily require its own
> > DOM, just some completion hooks similar to the existing ones. Things
> > like Goto Definition and Find References could operate at this level
> > as well.
> Some questions:
> 1) How do you do code completion without an own DOM? I mean you need to
> find out which construct the user wants to complete.
> 2) How do you do Find References without an own DOM? Don't you need to
> traverse the language specific DOM for it?
> 3) Same for goto definition. (need to find out which construct etc.)
I think you are misunderstanding Levi. I think he means that the code
completion window (the GUI component) doesn't need its (its==code
completion window) own particular DOM, and that a set of completion
hooks should suffice. If I understand it correctly, he is talking about
displaying the information, not about generating it.
More information about the Monodevelop-devel-list