JTreeTable

"Tim Lebedkov" <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.tasklist.devel
Message-ID <005001c2c7ae$f6e67310$d4c4c4ac@timpc>
Hello,

I spent yesterday some hours and replaced TreeTableView with JTreeTable from the Swing Connection
(http://java.sun.com/products/jfc/tsc/articles/treetable2/index.html). 

There are some advantages by using this component:
+ it allows you to scroll the whole component horizontally. Not just the first column.
+ it allows you to rearrange all the columns (the first too)
+ it is model-based (!). We will be able to write a model for our Tasks. It will help us reduce memory consumption and 
  improve performance as we only need to maintain one tree of objects and a model (currently we have at least 4 levels of 
  objects: Tasks, TaskNodes, FilteredTaskNodes, VisualizerNodes and hundreds (OK, maybe dozens) of listeners).
+ we will have full control over the component and will be able to resolve some bugs

There are also some things now that are not implemented:
- sorting
- turning columns off/on

What do you think about it?

I could implement as the first step a component based on JTreeTable that behaves just like TreeTableView and uses NodeTableModel.
As the second step models for our views could be implemented. I wrote an issue against the openide module 
(http://www.netbeans.org/issues/show_bug.cgi?id=30447 Swing compatible TreeTableView) and asked for a model-based TreeTable.

Tim
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.