I did a quick test with the TableView: I created a table with 30 columns and 10000 lines, full of values. When I scroll up and down, the table has trouble keeping track of the current position and drawing appropriately. I can see that it is eating up CPU as well. Doing the same thing with a swing JTable, this was completely fluid. This leads to several questions:
- if I was not using prism, why is the JTable still looking better than the TableView? Is that a problem of optimization in the TableView
- is that a goal for the GA to optimize it in such a way that it (out?)performs at least to the level of the JTable?
- if I was using prism, will the TableView then compete with the JTable?

In short, what I have seen in terms of performance was disappointing, and I am wondering if this is just a matter of not using GPU, or if this is a problem with the control itself, or both. I would hope to have decent performances even without prism, because there old configurations out there, and I cannot tell everybody to change their graphic cards just to do some scrolling ion a table...
see comments: http://fxexperience.com/2011/06/indeterminate-checkbox/comment-page-1/#comment-20840

I attached a simple application that shows this issue