Re: [anjuta-devel] [anjuta-list] The road to anjuta 3.4

[Sébastien Granjoux <seb sfo free fr>]

Hi,

On my side, I plan


* Improvement of the project manager GUI:

** Change the Add Source dialog to include a GtkFileChooserWidget widget 
and a combo box for selecting the parent.

** Use the same combo box instead of a tree view in Add target, Add 
directory and Properties dialog

** Allow to add module (https://bugzilla.gnome.org/show_bug.cgi?id=474993)

** Check if LT_INIT is present in configure.ac when adding a library 
target (https://bugzilla.gnome.org/show_bug.cgi?id=356416)

** Improve the navigation in the project view 
(https://bugzilla.gnome.org/show_bug.cgi?id=591682). This is handled by 
GTK, I'm afraid it will be quite difficult to get a patch here.

** Add an help button on project dialog opening Mallard documentation.



* Improvement of the project manager itself:

** Support non recursive makefile.

** Support custom m4 macro 
(https://bugzilla.gnome.org/show_bug.cgi?id=642785). I'm not sure it 
very useful.

** Support += operator in makefile 
(https://bugzilla.gnome.org/show_bug.cgi?id=650743).

** Support conditional variable 
(https://bugzilla.gnome.org/show_bug.cgi?id=646532). It looks quite 
difficult to implement.

** Add an ID for project property. Perhaps this feature could be useful 
to allow the symbol db plugin to get additional include directories. By 
example when using library not using pkg-config, you can just add to
CFLAGS -I/usr/include/something. If the project properties have standard 
name, the symbol db plugin could request for the CFLAGS property and 
check this value.

** Better handling of quote 
(https://bugzilla.gnome.org/show_bug.cgi?id=644534). It looks not very 
easy and it doesn't block anything at the moment.


* Then other things those could be useful

** Optimize Anjuta startup and remove the splash screen. The goal could 
be to start as fast as gedit.

** Improve gdl to save window position. For the git plugin, it will be 
useful to keep position of hidden windows.

** Improve symbol db to work with verilog language. It's very close to C 
so I think the parser is not an issue but it would be interesting to 
have the hierarchy of all modules. I think it could be seen like child 
classes in C++ but I don't know if symbol-db plugin supports this currently.

** Integration of Lucas's work.


Regards,

Sébastien