>(*) TablePane should maybe be called GridPane? >and then TableView could simply be called Table?
In general, our naming convention is "Pane" for containers and "View" for components (we also have TreeView, ListView, etc.). >Such a base-class would make implementing other custom table-like things >(e.g. locked columns, row headers, spreadsheets) a lot easier, >particularly given how difficult it is to implement even a Grid class >(I've tried). Take a look at this demo: http://cwiki.apache.org/PIVOT/fixed-column-table-demo.html It shows how TableView can be used to create fixed columns. The source is in SVN. >(*) TableView comments > - TableView#RowEditor and it's related set/get should really be called >CellEditor, because it's not really row-centric. It can actually be used as either a row or cell editor, since it gives you information about both. See this row editor demo that Todd recently posted: http://cwiki.apache.org/PIVOT/table-row-editor-demo.html > - javadoc - the selection methods don't say whether they are row or >column based Good catch. Thanks. > - it would nice to be able to set components on the corner spaces e.g. >the right hand edge of the columns, above the vertical scrollbar. You can currently set the upper left scroll pane corner. Do you think there is a strong use case for setting the other corner components? > - It would be nice to define some standard mechanism of daisy-chaining >TableView#CellRenderer classes to implement things like row highlighting. I'm not sure what you mean here - could you elaborate?
