Re: JTreeTable

Hi Tor,

>
> I think approaching openide and getting the TreeTableView changes is the
> best approach. The TreeTableView is used in many other places (debugger,
> module manager, etc.) so it would be bad to fix this locally, not
> globally.

I tryed to solve http://tasklist.netbeans.org/issues/show_bug.cgi?id=27670.
It is very complicated to do this  using nodes.
The main problem is that after recreating the whole tree we lose node
selection/open state.

>
> We still need to Node APIs for getting property sheets etc. to work
> correctly.

TopComponent.setActivatedNodes(task.createNodes()) could be used to get
property sheets and other nodes
related things working

> It would however be nice to be able to create the nodes
> lazily (much like the way the table model allows you to only provide
> values for those rows that are visible in the table). So, instead of
> having to create all the children of the root node right away, it
> could ask for children in chunks.    If we're only creating nodes for
> the visible rows, we're not going to consume very many resources at
> all.

Filter is based on nodes (not on the tasks) so we need to create all levels
of nodes although
they are not visible.

> And it would allow most of the APIs to stay the same. The Children
> API would have to be changed in openide to allow dynamic node requests
> however.
>
> I think it would be a good idea to make your proposal to nbdev,
> since it involves some API changes, and affects multiple modules.

Tim