ok, but why do I have the heap space problem because I also have it if I use the server-side toggle. I can create the 26.000 nodes without any heap space problems but then if the tree2 controls tries to create the visible part of the tree I get a heap space problem. Can you imagine what the problem is?
2006/2/22, Sean Schofield <[EMAIL PROTECTED]>:
The tree already ignores nodes that are not expanded (in the
server-side toggle.) Its only the server-side toggle that does not
ignore them and that's because it can't. It needs the whole tree b/c
it needs to be able to show any/all nodes the user might decide to
expand.
Sean
On 2/22/06, Hans Sowa <[EMAIL PROTECTED]> wrote:
> Hi
>
> My heapspace configuration is min 32 max 128.
>
> Maybe it is a good idea to partially load the data. This should solve the
> problem with the heap space. But if I use the server side toogle I think it
> would be a good idea if the tree component would ignore the nodes which are
> not shown in the tree. Maybe this is an idea for a future enhancement.
>
> The other issue is the html code. Is there a possiblity to decrease the
> htmloutput. The html code for one node is really large and a big problem for
> the browser (especially for IE).
>
> Thanks in advance.
>
>
> 2006/2/22, Mario Ivankovits <[EMAIL PROTECTED]>:
> > Hi!
> > > Eventually I envision an Ajax version of the tree2 component.
> > >
> > +1
> > It will definitely be great to have a ajaxed tree2.
> >
> >
> > Ciao,
> > Mario
> >
> >
>
>
>
> --
>
> mfg Hans Sowa
> mailto:[EMAIL PROTECTED]
--
mfg Hans Sowa
mailto:[EMAIL PROTECTED]
