Re: [anjuta-devel] GNOME IDE

[Johannes Schmid <jhs jsschmid de>]

Hi!

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

I think this depends highly on the build system that should be used for
such a stand-alone application. What's the plan for that?

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

I think the exact implementation doesn't matter too much. We could even
think about creating special environments for different scenarios, like

gnome-ide-c
gnome-ide-javascript
gnome-ide-python

It might be just a matter of loading a different default session file
and storing the used environment somewhere so that some plugins (like
the project-wizard) behave differently.

Regards,
Johannes