Work is happening for this feature in the varobjs-support branch of the Nemiver repository.

You can inspect the code at http://git.gnome.org/cgit/nemiver/?h=varobjs-support .

At the moment, the backend support of the varobjs is more or less working.

I have ported the VarInspector type over the varobjs support. Now when you inspect a given variable in Nemiver (when you hit the F12 key) the variable inspector dialog uses variable objects.

I am currently porting the LocalVarsInspector type to variable objects as well. That is, the "Variables" tab at the bottom of the Nemiver screen. That should soon be in a more-or-less-working state as well.

More on this later.

Okay, I have pushed a set of patches to the varobjs-support branch that basically adds varobjs support to the local variables inspector widget. So now variable inspector and local variables inspector both support varobjs.

To try it, you have to configure that branch with --with-varobjs.

I will be testing/debugging/ that branch for a little while I guess.

So the varobjs-support branch seems quite usable for me. I have been using it daily for 2 weeks, ironing it out etc, and it seems to perform better than what we had previously. I have even added variable value editing on top of it.

Now that Nemiver 0.6.7 is released, I think the varobjs-support branch is going to be merged in master soon.

I the varobjs-branch has been merged into master.

So what do we get in now ?

The VarInspector widget, LocalVarsInspector and VarInspectorDialog are all varobjs powered now. As a bonus point, we can now edit the value of a variable and set hardware watchpoint on some variable expressions.

This should fix a couple of bugs as well.

I guess What remains is to port the variable tooltip over varobjs as well.

I think I can now close this bug.