Data Binding for Table UI Element
A Table receives its data from a context node. Therefore, the Table property dataSource has to be linked to a multiple context node.
At runtime, each node element of the node collection is a row.
The number of rows is identical to the number of node elements. The selected rows correspond to the node selection. If the selection of the context node changes, the selected rows also change.
The columns usually correspond to the context attributes (but do not have to, see below) and are described through an aggregation of TableColumn objects. They specify the number and order of columns as well as the headers and the width of the columns.
The content of a cell to be displayed is specified by the table cell editor ( TableCellEditor) of the column. The TableCellEditor can only display the content in a cell, so it does not make any difference if the content cannot be edited. The following TableCellEditor s can be selected:
|
UI Element |
Description |
|---|---|
|
Button FileDownload FileUpload LinkToAction LinkToURL ValueComparison |
UI elements that can be used to trigger events. We recommend that you do not use a Button in the Table due to its problematic design. |
|
Caption Image ProgressIndicator TextView |
UI elements that can be used to display texts or graphics. Note
If texts are too long, they are wrapped in TextView, which can spoil the layout of the Table. To prevent this, use the fixedTableLayout mode of the Table and set in TextView wrapping=false. |
|
CheckBox RadioButton DropDownByIndex DropDownByKey |
UI elements that can be used to select elements of a specific value set. |
|
InputField |
Allows cell content to be edited |
The content to be displayed in a Table does not have to be identical to the data source of the Table. For example, two columns can display the same context attribute or two context attributes can be displayed in the same column.