[MonoDevelop] Mono, MonoDevelop and other IDE's

Todd Berman tberman@off.net
Tue, 19 Oct 2004 10:52:04 -0700

On Tue, 2004-10-19 at 18:36 +0100, Alexandre Gomes wrote:
> I'm suggesting to implement components to Anjuta. 

Why? Anjuta's development is totally stalled, and its written in C.

> I'm suggestion a more 
> clear separation of those components so it could be possible to make MD more 
> flexible as well as use that components in another IDE's. If those 
> components where clear enough I could build a warper with C and design a 
> plugin to Anjuta, Eclipse or another IDE.

It already is. Have you looked at MD's source? (I know, it can blind you
and make you insane). Just about everything (Including the main window)
is a plugin.

As far as cross-IDE plugins, uh. not possible.

First, you are talking about 3 different apps, written in 3 different
languages using 2 different windowing toolkits. Second, the word
'plugin' means that it plugs-into-something. That something is pretty
app-specific always. It has to be, otherwise the plugin can't really do

> Think of MonoDevelop as a base where you can choose different project 
> managers, different source editors, etc... thats another advantage since 
> plugins are nice but they can't control everything (example: themes).

That is a totally awesome idea. Wait. Wait. Oh, thats right, thats
*exactly* how it is already set up! Your work here is done dude!