On 8/9/06, Al Gilman <[EMAIL PROTECTED]> wrote:
Like the label for a form control, there should be both a nested version and a threaded version.
Allowing an optional for attribute might make sense, but you don't need it for this use case. On the other hand, this tree-view is a perfect example of why you might want arbitrarily nested rowgroups. -jJ
This view is typical in file-system browsing at present. There is a table. The first column is an index to the rows in the form of a tree that you can fold or unfold. The remaining columns give properties of the entries in the tree-shaped index. In other words, the structure of the collection of rows is a tree but the structure of the collection of columns is a list. [both could have tree structure, but most commonly only the collection of rows does.]
In this case, to capture the full semantic structure we have to thread the first column of cells together with structure outside the parse tree. The table structure makes each of these cells just the first cell in its row; and the cells in the row is the inner loop of iteration and the rows in the table is the outer loop, as represented in the XHTML linearization.
