On Mon, 2005-05-23 at 14:41 -0400, Sean Schofield wrote:
> > When working with trees with many nodes, the browers seem to have
> > difficulty with all the html being rendered with clientSideToggle=true.
>
> What do you mean trouble? I assume you are talking about a performance
> problem.
If I attempt to load a tree that has say 8000 nodes, the browser will
spit out an "Out of Memory" error. But this only happens with the large
client-side trees.
>
> > So what I have tried was to set the clientSideToggle to be a
> > valueBinding so I could change this based on the number of nodes the
> > tree was going to have. But I ran into a bit of a snag, seems that the
> > clientSideToggle attribute does not accept or reconize value binding. I
> > am not sure if anyone else might find this useful or not... but just an
> > idea, I figure it should be a simply modification to the TreeTag.
> > Thoughts?
>
> It seems like you would normally know the answer to this question
> ahead of time. Either the data will have < 200 nodes or more than 200
> nodes (200 is an arbitrary number, it can be whatever number at which
> the performance starts to slow.)
>
No, I am using the same treeAdapter to display the same tree for all
users. However, based on the user's security, the tree can be just a few
nodes, to several thousand nodes.
> My gut instinct says this feature will only be useful in limited
> situations and that adding code to handle this special case might be
> overkill. I'll keep an open mind so if someone can persuade me this
> is something that could be used in more than in a special case then I
> will be open to a patch.
So I was thinking something like <x:tree2
clientSideToggle="#{treeBean.clientSideToggle}" ...../>
>
> > Tim Pyle <[EMAIL PROTECTED]>
>
> sean
--
Tim Pyle <[EMAIL PROTECTED]>
