Not sure I understand the question. Each object
represents a row, not column, and the content provider provides the
child/parent relationships of the modely by answering the hasChildren and
getChildren questions. It's up to the model and the code that creates it
to come up with the relationships and provide those to the
treeviewer.
Maybe you can point to an example of what you mean by
chaining model objects together.
I am playing with the example and
couldn’t find a way to group columns to build a tree view? There is a picture of
a XViewer with tree/table view on the Nebula XViewer Web page. I guess my
questions are; 1) Is there a way to dynamically build a tree view in the table
by selecting model objects (columns) and connecting them together? If so, is
there an example of that in the example code? If not, can it be done in XViewer
without having to write custom TreeViewer code to support every possible
combination of model relationships the user may choose? There are several
examples from other products out there that allow you to chain model objects
together and create a tree/table based on the relationships of the objects as
defined in the model. Anyone played very extensively with the tree part of the
XViewer?
Thanks
|