Hierarchical tables
The other half of the hierarchical tableselect example: the administrative tables of a tree that select nothing, which is most of them. A book outline carried by indentation and dragged into shape, with a text field in its first cell; a manage display form, whose tree is region grouping rather than indentation and whose rows carry five widgets each; and the same tree printed rather than administered. The trees are made up and nothing is saved.
A tree with nothing in it to edit
The same outline printed rather than administered: a table of rows, no form element in any cell, and no form around it either. It is what a list builder outputs, and it is worth having under the two forms above because almost everything a theme does to a table of widgets -- the height of a row, the space around a cell, the alignment of a column -- was decided by the widgets and is wrong here. Two things this table can afford that neither form above can: a caption, which names the table to a screen reader without a heading, and a row header in the first cell, which a table of controls cannot have because the header of a row is no place for the control that operates on it.
| Title | Pages | Updated | Operations |
|---|---|---|---|
| Getting started | 4 | ||
| 2 | |||
| 0 | |||
| 0 | |||
| Theming | 3 | ||
| 0 | |||
| 0 | |||
| Deployment | 0 |
The tables with a column of check boxes or radio buttons in front of the tree are on the hierarchical tableselect example, which is the other half of this one. The two forms these are all modelled on, reproduced rather than varied, are on the menu and taxonomy overview example.