It would be nice if the footer of the kendo treelist didn't disappear when the table is in scroll mode. I think it would be more beneficial if the footer were stagnant similar to the kendo grid.
I would like to use drag and drop on treeList to reorder rows (with same parent) like on treeView or at least to have same events (drag, dragstart, dragend, drop), where I'll be able to change behaviour.
Is there any support for checkbox columns in the treelist to behave the same way as the kendoTreeView checkboxes? (ie, checking or unchecking parent should check/uncheck all children? and checking or unchecking children should update parent check state (possible indeterminate states))
When you add keybord navigation to the TreeList, alongside with the ability to drag and drop TreeList rows, keyboard events won't fire. http://jsfiddle.net/ahz94f1j/2/ It looks more like an simple oversight, but we asked suppport and they responded that we should make a suggestion here.
It would be nice if there was an option to not retotal the entire table if you expand a level in the treelist. We use the table for lazy loads, so each level already has the total, we're just getting the details.
It would be nice to have an option to repeat the headers within each level of the tree list. This would allow a user to sort within the level. We have large datasets with lazy loads. We could use the grid control and embed a table within the grouping but users like how the columns line up in the tree list.
As discussed on the forum (http://www.telerik.com/forums/virtualization-for-treelist) please improve the rendering/scrolling/expanding/collapsing performance of TreeLists with many expanded rows. Grids support virtualization and work well with hundreds of thousands of rows (http://demos.telerik.com/kendo-ui/grid/virtualization-local-data). Perhaps virtualization can be added to TreeLists to achieve similar results?
lets set the page size of treelistview and provide the endless scrolling feature along with the paging on the grid. When the user will scroll up/down the respective page from where the latest data being fetched should be selected and user should be given the flexibility to move to next page. This way user can move to the desired data (say last) using paging and enjoy the endless scrolling too.
Great work on this control boys.... I reckon it needs Filter Row, Multiple Column Sort, Paging to make it consistent with the grid. Regards, Scotty