Thanks, Mark. IT does look like there's new stuff.
The prose on http://demos.kendoui.com/beta/web/treeview/odata-binding.html
indicates that it does NOT support dynamic binding but the code in the example does.
I hope they document this well as its hard to infer everything from just the examples.
There are 2 situations you might want to use dynamic binding.
One is that the server has a large, static database that a user wants to browse.
Since a given user will probably never expand all nodes, there's no need to send the whole db to the
client. Letting the client ask for children by expanding a node is fine.
The 2nd situation is when the data on the server is changing while a user is browsing the db.
In my case other users can add, delete, edit and move nodes in the tree while a user is browsing.
There are 2 ways I can think of to support this
"The cheap way": Always display the expansion triangle. (I guess you can always declare hasChildren; true) Whenever the user expands, a call to the server
happens to get the kids.
"The Smart Way" UI pays attention to the hasChildren flag and shows or hides the triangle appropriately,
but ALSO the app is written using HTML5 Channels such that the server keeps track of which users have which
parts of the tree open and pushes new information to the client, including added/deleted/changed nodes as well as
updating the hasChildren flag on a given node. For this to work, the client would have to
be able to set "hasChildren" for a given node and have that display/hide the triangle.
My biggest fear is that neither of these ways will work because the new Kendo dynamic binding might only go to the server
the FIRST time a node is expanded and from then on it caches the results on the client and the client just
displays the cache, not goiing to the server for the 2nd thru nth expansion of a node.
I would be a big help to me if you could tell me whether such caching is done on the client.
If not, then a user can at least collapse a node then re-expand it to "refresh" the children to check
if anything has changed since their first expansion.
To implement "The Smart Way" there would need to be a method to call on a node on the client to
change hasChildren and have that call automatically show/hide the triangle. In viewing the methods
on the Beta page for TreeView there don't appear to be any such methods. I also don't see any configuation
options about caching nodes on the client.