---------- Forwarded message ---------- From: Sean Schofield <[EMAIL PROTECTED]> Date: May 10, 2005 1:00 PM Subject: Re: Re: tree component & folder icon To: "Virtudazo, Dennis (Exchange)" <[EMAIL PROTECTED]>
> Anyway, I created tree2table renderer and tag. The main problem with > client-side collapse/expand is that html span doesn't work interspered > among table rows. Hiding the rows themselves is possible but the > javascript has to hide/show each row individually (many rows versus the > current hiding on just a single span element). So a rewrite of the > javascript for treeNavClick is needed. I seemed to recall this being the major issue. > I found that I actually needed to override the encodeTree method because > I need to modify the writing out of span elements. I'll have to take a look at the existing code to refresh my memory and see what you're talking about. > The table columns btw, I'm thinking will have to be defined as <column> > tags within the tree2table. It is easy enough to cache the column > components so that they can be rendered for each node of the tree. But I > haven't made it work to render real columns yet, just hardcoded columns. This also sounds familiar. Do you think treetable would be manageable without the client-side javascript? Would it be worth it to implement without client-side support? I'd be interested to see the "ideal jsp" you would use to configure the treetable - regardless of whether we give up on javascript or not. Also, for those javascript-meisters out there ... feel free to look at the problem Dennis is describing and see if there is an *elegant* solution to our problem. sean
