AW: UML CanvasItem

Hi All,

 

since my Gentoo/Linux crashed I was blocked.

This night my xorg-x11 compiled the first time and the gnome

sources are compiled the hole night. I think that the my system

is usable during the weekend. Sorry for that system story ...

 

Since everything is installed I will write a simple Addin for MDev

for simple loading a XMI diagram. I want to use the MUml code

for that.

 

I agree that MDev design is goog to integrate all the stuff, that are

necessary for a Solution-Project based tool, but also the MUml

standalone version makes sense.

 

I want to use all the sub-components like the docking stuff, toolbar,

workbench, solution pads etc. because I know how difficulty it is

to implemented this thinks again and again. I did it once with the

MagicLib with MS Visual Studio .NET.

 

So I was glad to see, that the SharpDevelop port (MonoDevelop) uses nearly the same

concept/design. This will help a lot!

 

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?

 

Thanks a lot

and a nice WE

 

Jörg

---

Von: monodevelop-list-admin@xxxxxxxxxxxxxxxx im Auftrag von Lluis Sanchez
Gesendet: Di 05.04.2005 14:49
An: Mario Carrión
Cc: monodevelop-list@xxxxxxxxxxxxxxxx
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
> <joerg.rodehueser@xxxxxxx> 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 a
> 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 a
duplication of efforts and code).

Lluis.



>
> Cheers

_______________________________________________
Monodevelop-list mailing list
Monodevelop-list@xxxxxxxxxxxxxxxx
http://lists.ximian.com/mailman/listinfo/monodevelop-list