I actually have the same problem with tacos trees. :) The first step in a solution has been solved by making the tree Partially renderable, ie ajax capable. This does however still require an initial load of the tree, and depending on your tree's size this could become very unwieldy.
The second stage in making the tree handle large data sets is going to be something along the lines of either providing "live-grid" like behaviour, where as you scroll down the tree it dynamically requests more tree nodes (if it doesn't already have them), or the more simpler solution of providing tree "paging" navigation links. Ie forward/backward/jump to /etc.. This would be supported in ajax or non ajax modes. The current tree I'm rendering can potentially display tens of thousands of nodes (if they were all expanded), so I understand your problem very well :) jesse On 9/8/05, Tapestry Stuff <[EMAIL PROTECTED]> wrote: > > Hi, wondering if anyone has come up with a nicer way to present LARGE sets > of hierarchical data. Trees are fine but the large set makes the tree > unwieldy. We have been using tacos tree for a long time but now the set > has > grown so large as to cause us grief with page layout and looong db > queries. > I think that persisting the tree is out of the question as the set is too > large. > > Any ideas? > > -- > Nick > >
