jQuery tree grid displays data in a hierarchy, it supports loading data locally and remotely. Treegrid is built on top of grid, so it borrows and supports same features as of grid except few minor differences as mentioned below:
It's mandatory for every row ( parent as well as children nodes ) in treegrid to have unique id field.
The data can be in either nested or plain format.
beforeTreeExpand, treeExpand, beforeCheck, check.
pq_tree_cbhidden column with an editable callback.
Checkbox states are saved in
rowData.pq_tree_cb by default as true, false or null (indeterminate states).
All checked rows can be found by a call to
They work the same in grid and treegrid, so beforeRowSelect, rowSelect event and SelectRow() API can be used for treegrid too except a minor caveat in case when row selections are bound to checkboxes as mentioned.
SelectRow object has two categories of methods: one to manipulate the row selections and other to read state of selections.
When checkboxes are bound to row selections, only the second category of methods of SelectRow() API to read state of selections can be used.
To manipulate row selections, checkbox selection API of
Tree() should be used. beforeRowSelect, rowSelect events are not fired, instead beforeCheck, check
events are fired.
Custom icons can be displayed beside the nodes with help of
treeModel.render callback as done in this example for `license.txt` node.
The data in columns can be summarized at every change of hierarchy level in two ways:
treeModel.summary is true, values in all children nodes of a parent are summarized and displayed in a separate summary row at its bottom
treeModel.summaryInTitleRow is true, values in all children nodes of a parent are summarized and displayed in the parent node itself. No extra summary row is generated in this case.
Treegrid is not compatible with paging.