I didn't remove the contents within the elements(<ul>data</ul><li>data</li>). I
only had to remove the html and (<div></div>, etc) attributes/characteristics
applied by treeview, cause on a rebuild it would reapply the attributes,
resulting in it breaking.
I had to bring the lists down to the simple html and then rebuild.
I'm not sure how someone else would have gone about this, but there's not
much info around on working with trees to make them as dynamic as I needed to.
I'm not sure why you write about removing the contents in a <ul></ul>? At
what point would that beneficial? Your working with the ajax tree, but how much
ajax interaction are using? Only at onload time?
rolfsf <[EMAIL PROTECTED]> wrote:
Thanks ripple.
So are you saying you had to remove and clear the individual elements
and attributes, rather than using empty() or remove() on the UL?
Why wouldn't removing or emptying the contents of the UL do the same
thing?
I guess I'm confused as to what or where (why!) information about the
contents of the UL is being cached if we've reset it to an empty ul>
rolf
On May 1, 8:13 am, ripple wrote:
> I had to handle this situation over a week ago.
>
> I just wrote a couple lines to remove all tree attributes from the
> generated source and then rebuilt the tree.
>
> $('.sample ul:eq(0)').removeClass('treeview');
> $('.sample li').removeClass();
> $('.sample ul div').remove();
> $('.sample ul').removeAttr('style');
>
> $('.sample ul').tree();
>
> See my working sample
> here.http://www.2whoa.com/apps/demo/apex-admin/hierarchy.html
>
> Works great on IE6 and FF. Haven't tested it on a Mac yet.
>
> I hope that helps.
>
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
