[MonoDevelop] Request for Mission Statement

Miguel de Icaza miguel@ximian.com
Thu, 08 Jan 2004 13:13:44 -0500


> IMO it's really good to integrate all those softwares in MD, but i think
> you should consider the process as a component integration: in the end
> .net is just about components.
> I'm not looking at bonobo, here bonobo is useless, the object model is
> .net
> I'm speaking about treating monodoc, mono-debugger, nunit-gtk, perhaps
> sql# as components that can be plugged inside MD or can be run alone.
> To see an example consider msdn browser, it runs inside vs or as a
> standalone application (I guess it's the same code maybe it's not).
> Ultimately I see that the experience from bonobo can helps a lot.


monodoc and nunit-gtk have their own UIs today, and we will have to
find a way of hosting them in MonoDevelop.

But the debugger does not, and I am having trouble doing a UI only for
it.  So this is the perfect match.

Notice that the debugger will still be available as a class library and
as a command line tool, so others can still develop different
interfaces (graphical or not).