Re: [anjuta-devel] New project interface and introspection

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

Hello,

I have changed the project manager and the autotool backend to use the 
last IAnjutaProject interface (with 4 signals and without using thread 
in the project manager).

I haven't changed the directory backend so it's probably not working.

The autotools backend doesn't use thread now and I can see the 
difference. The GUI is frozen for a few seconds after start up here, I 
will restore the use of threads in a following commit.


I have found one issue when reloading the project. Currently, the other 
plugins access project node using the GFile object which is annoying 
because several nodes could refer to the same file. I have planned to 
use AnjutaProjectNode instead.

Previously, to reload a node, I make a copy of the node without its 
children, recreate all its children, and then replace all these new 
children in the project tree. If the same node was already existing, the 
item in the project tree view is the same but point to another 
AnjutaProjectNode object.

Now, as we plan to use these AnjutaProjectNode object, I think they 
shouldn't change if an already existing node is reloaded. Especially 
because a reload can be triggered automatically if a project file is 
modified. I have token care of this but it's difficult to do. Do you 
have such issue in your backend ?

Or do you think it's acceptable to destroy all AnjutaProjectNode and 
create new ones when a part of the project is reloaded ?

Regards,

Sébastien