[Gtk-sharp-list] Ways of supporting complex data binding in TreeView

Mike Kestner mkestner at novell.com
Tue May 31 13:03:33 EDT 2005

On Fri, 2005-05-27 at 15:58 -0700, Chas wrote:

> The biggest question as far as I can tell is - which
> of the described options is better, the 'synced'
> liststore or the 'referencing' liststore? Maybe we
> need to support both? Or do someone have another idea?

The way I envision data bindings in TreeView is to add a DataSet
property to TreeView itself instead of exposing a public TreeModel.
Under the hood this would instantiate an internal TreeModel
implementation that binds the typed list to the TreeView and sets up all
the TreeViewColumns appropriately.

I think this approach is superior to a public TreeModel because people
who want to use data bindings are not going to want to have to format
the TreeView manually.  We already have magic in NodeView that does this
kind of auto formatting of the view.

Todd already pointed out that unless we want to write another hybrid
native/managed model like NodeStore, GInterface implementation is a

Mike Kestner <mkestner at novell.com>

More information about the Gtk-sharp-list mailing list