[Monouml-list] Re: AW: [MonoDevelop] UML CanvasItem
Sun, 10 Apr 2005 11:30:44 +0100
On dv, 2005-04-08 at 12:30 +0200, Rodehueser, Joerg wrote:
> Lluis, one question for you:
> Do you know where the source of the "source code parser" is placed in
> the source-tree?
> Exist an interface for source code parsing?
> Whats the output?
The parser service is defined by the interface IParserService and you
can access to it from Runtime.ParserService. Right now the interface is
mainly oriented to code completion, and some additional methods may be
needed to be useful for an UML tool, but this should not be a problem
since all needed information is there.
The service returns IClass objects, which contain all information about
a class: fields, properties, methods, events, nested classes. You can
also get the region in the source files for all of those elements.
The service also provides events that are fired when parse information
change in the source files, so you could use them to update the diagrams
on the fly.
> Thanks a lot
> and a nice WE
> Von: firstname.lastname@example.org im Auftrag von Lluis
> Gesendet: Di 05.04.2005 14:49
> An: Mario Carrión
> Cc: email@example.com
> Betreff: Re: [MonoDevelop] UML CanvasItem
> On dv, 2005-03-25 at 14:32 -0600, Mario Carrión wrote:
> > On Fri, 25 Mar 2005 17:44:39 +0100, Rodehueser, Joerg
> > <firstname.lastname@example.org> wrote:
> > > Hi All,
> > Hi
> > > I want to write a UML plug-in for MD. I startet to look at the
> gnome libs
> > > and I found
> > > the gnome canvas and its item.
> > Why don't you port some of our work to MonoDevelop?
> > http://monouml.sourceforge.net
> > If you want you are welcome to our team. One of our future goals is
> > full integration with Monodevelop.
> I think it would be a good idea to take MonoUML as a code base for a
> MonoDevelop UML addin.
> One of the goals of MonoDevelop is to be a platform flexible enough to
> allow the implementation of any development tool on top of it. Those
> tools can take advantage of all MonoDevelop services, such as:
> * A project system.
> * A source code parser.
> * Better support for background operations.
> * Extensible menus and toolbars.
> * A docking layout.
> * etc.
> I say "implementation" and not "integration", because ideally there
> should be no need for a standalone version of the tool (which would be
> duplication of efforts and code).
> > Cheers
> Monodevelop-list mailing list
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Monouml-list mailing list