> For our tree, we render the entire tree on every request, so that the > user could expand/collapse it as far as they like w/o a reload.
This is how the "client-side" version of the tree will work. It will use javascript to do this. > Originally, we built flags into the model such that you could declare > certain leaves to reload the page if expanded. This way, if you had a > huge tree, you didn't have to render it all at once. It was sort of a > compromise between a strictly server-side and client-side tree. We will have something like this in the new tree as well. Actually it will behave the same as the current tree. The tree starts out collapsed and as the user opens nodes, more data is loaded into the model. sean
