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

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

Hi Abderrahim,

Le 06/09/2010 18:22, Abderrahim Kitouni a écrit :
> Yes, that's right. The structure can be marked as foreign but then
> static bindings have to be written (somewhat defeating the purpose of
> gi).

No, you just need to provide access and set functions for everything, 
like it is done for AnjtuaProjectNode.

> Yes, it's not strictly needed, I was just thinking about getting rid of
> free_node.

Ok, but if this case you need to use a GObject of at least a boxed type. 
For a GObject, you can derive your own node type, for a boxed type,I'm 
agree, it would be nice to provide a destroy notification callback.

> Theoretically, it is temporary. But in practive, it can be some time
> before it's fixed in all bindings. (And personally, I think we don't
> need to worry about a limitation if it's only in one binding. We can say
> e.g. a project backend cannot be implemented in js for now).

Ok, that's fine for me if it's temporary. If we really want it we can 
always help.


> And even though gnome-shell is successfully using signals as workarounds
> (see ShellGenericContainer), I actually think signals are good in this
> case : a Group node for example could connect to the signal on itself as
> well as on child nodes, and get notified if they need to be saved.
> (This still needs more thought, but you get the idea)

Ok, I will look at this.

Regards,

Sébastien