[MonoDevelop] Mono, MonoDevelop and other IDE's
Tue, 19 Oct 2004 18:36:54 +0100
I'm suggesting to implement components to Anjuta. 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.
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).
>From: Todd Berman <firstname.lastname@example.org>
>To: Alexandre Gomes <email@example.com>
>Subject: Re: [MonoDevelop] Mono, MonoDevelop and other IDE's
>Date: Tue, 19 Oct 2004 10:29:39 -0700
>On Tue, 2004-10-19 at 16:36 +0100, Alexandre Gomes wrote:
> > The way I think is:
> > -The project management tree handling the project tree and the templates
> > -The source editor with sintax highlight and auto completation
> > -The compiler/make creator
>I am not sure what you mean exactly.
>There is no reason (that I can see) to attempt to integrate MD stuff
>First, Anjuta is a completely different app that doesn't use C#. To
>integrate the two, Anjuta would have to take a dep on Mono, which I
>really just dont see happening at all.
>Second, Anjuta provides little outside of what we already have, and that
>little is cvs support. Writing cvs/svn/etc support into MD is a far more
>managable task than attempting to get MD components running inside
>Anjuta. And with far better payoff.
>Maybe you should start out by explaining why there is any advantage for
>MD components to be usable inside Anjuta, because, from here, it looks
>Monodevelop-list mailing list
MSN Messenger: converse com os seus amigos online.