Re: [anjuta-devel] (no subject)

[Abderrahim Kitouni <a kitouni gmail com>]

Hello,

Le jeudi 31 janvier 2013, a écrit :

As Anjuta is very flexible, I think it's possible to use Anjuta to implement
this GNOME application IDE even if I would like to keep the current goal because
I think it's what is making Anjuta different from other IDE. In my mind,
implementing this GNOME application IDE would be an interesting experience and
would benefit to Anjuta as a big part of code can be common.

I agree.

 

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...

Yeah, since we are starting afresh (i.e. we don't have to support e.g. autotools), we can use another build system, maybe even something designed for this purpose.

 

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.
- Create a new executable which can use the same plugins.
- A last option is to not use Anjuta at all.

 

What do you think?

I think either option 2 or 3 would be fine. Since gnome applications don't have branding, this would mean we can keep the Anjuta name for the full-fledged IDE, and the gnome IDE would be the simplified version.

Regards,

Abderrahim