Re: Back to the roots

Tim Lebedkov wrote:

> Hi,
> 
> compiler submodule currently does not use TreeTableView to present build
> messages.
> It uses another JTable-based component. I finished the development of
> this component
> and in order to make the module more compatible to the other submodules
> I plan to do something with it.
> 
> Alternative 1 (I don't have any illusions. It will be probably not
> accepted.):
> ------------
> - change the tasklist/core to use this new component
> 
> Alternative 2:
> -------------
> - change the /compiler submodule to use TreeTableView

Tim be in touch with Tim. You are only experts on TreeTable[View]
kind of components. I do not know all implementation UI-features
so for me wins one with simpler data model API. Right now
TreeTableView because Tor already implemented Node-based layer.

> - Petr, Would it be possible to reuse the code from "TODOs" view? I
> think "Build Messages" view should look similar.

Have I forgotten to scatter some final or private keywords? :-)
I think that the view is rather specialized so I suggest
primitive copy&paste. What do you mean exactly? If possible
I'll factor it out to a utility method or new core class.

> FYI: org.netbeans.modules.tasklist.compiler.treetable.TreeTable
> --------------------------------------------------
> 1. It is now ready and implement all features that TreeTableView has
> (sorting, column hiding, filtering).
>   ( I already informed Tim Boudreau and it could be used to reimplement
> TreeTableView.)
> 2. It is faster than TreeTableView (I didn't make any tests. It's just a
> feeling)
> 3. It is possible to reoder the first column
> 4. It is possible to create a complex cell renderer (e.g. java syntax
> highlighting could be implemented easily)

The biggest advantage from my quick look is the model interface
and explicit renderer setters. You can either write a bridge
to Nodes or work with Tim to propagate them to openide TTV.

Raise the issue on broader list after some discussion with Tim.

  Cc.