Re: [anjuta-devel] (no subject)



Hi Sebastien,

Am 31.01.2013 17:33, schrieb seb sfo free fr:
To be more practical, I think one main change is to write at least a new project backend plugin instead of using the autotools backend. I think it's needed to present a simple interface to the developer. By example having a simple combo list to select the targeted platform (GNOME 3.6, GNOME 3.8...) instead of a big
list of available libraries, hiding C compiler flags...
It seems to be the best way to write a new plugin for this.

I think we could implement this GNOME application IDE by writing new plugins and probably modifying a bit some existing one to be sure that it runs smoothly. By example, one modification is to hide plugins not useful for GNOME application IDE (like makefile backed, autotools backend...). It can easily by done by adding an attribute in each plugin. Then, I don't know if we should have - an option in Anjuta checked by default to show only GNOME application plugins,
this will effectively change Anjuta.
- call Anjuta with a different name but using the same executable.
What do you mean here? Two ways to start Anjuta: One with the old behaviour (our current Anjuta) and one with the new GNOME application IDE features? If that's what you mean, then I prefer this option.

- Create a new executable which can use the same plugins.
- A last option is to not use Anjuta at all.


Regards,
Moritz



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]