The Table namespace is getting somewhat cluttered, and will become more so as
additional Data Cell Renderers are soon added. It seems worthwhile to split
up this single-level namespace into an appropriate hierarchy.
The current structure looks like this:
% tree table
table
|-- AbstractDataCellRenderer.js
|-- AbstractResizeBehavior.js
|-- AbstractTableModel.js
|-- BooleanDataCellRenderer.js
|-- CellEditorFactory.js
|-- CheckBoxCellEditorFactory.js
|-- DataCellRenderer.js
|-- DataRowRenderer.js
|-- DefaultDataCellRenderer.js
|-- DefaultDataRowRenderer.js
|-- DefaultHeaderCellRenderer.js
|-- DefaultResizeBehavior.js
|-- HeaderCellRenderer.js
|-- IconDataCellRenderer.js
|-- IconHeaderCellRenderer.js
|-- RemoteTableModel.js
|-- ResizeBehaviorColumnData.js
|-- ResizeTableColumnModel.js
|-- SelectionManager.js
|-- SelectionModel.js
|-- SimpleTableModel.js
|-- Table.js
|-- TableColumnModel.js
|-- TableModel.js
|-- TablePane.js
|-- TablePaneHeader.js
|-- TablePaneModel.js
|-- TablePaneScroller.js
`-- TextFieldCellEditorFactory.js
0 directories, 29 files
I propose something more like this:
% tree /var/tmp/table
/var/tmp/table
|-- SelectionManager.js
|-- SelectionModel.js
|-- Table.js
|-- TablePane.js
|-- TablePaneHeader.js
|-- TablePaneModel.js
|-- TablePaneScroller.js
|-- celleditorfactory
| |-- CellEditorFactory.js
| |-- CheckBox.js
| `-- TextField.js
|-- datacellrenderer
| |-- Abstract.js
| |-- Boolean.js
| |-- DataCellRenderer.js
| |-- Default.js
| `-- Icon.js
|-- datarowrenderer
| |-- DataRowRenderer.js
| `-- Default.js
|-- headercellrenderer
| |-- Default.js
| |-- HeaderCellRenderer.js
| `-- Icon.js
|-- tablecolumnmodel
| |-- TableColumnModel.js
| `-- resize
| |-- Resize.js
| `-- behavior
| |-- Abstract.js
| |-- ColumnData.js
| `-- Default.js
`-- tablemodel
|-- Abstract.js
|-- Remote.js
|-- Simple.js
`-- TableModel.js
8 directories, 29 files
Making this change will require migration support, since, of course, it makes
non-backward-compatible changes. This change, therefore, should not be done
until someone is able to allocate the time to work on the migration script.
I'm not wed to either this particular structure or the absolute need to change
anything, but it does seem that the status quo will become more and more
difficult to maintain as time goes on and new contributions are added.
Thoughts?
Derrell
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
