Sean Schofield wrote:
The tree just happens to be the object with the methods you are
calling. The method will indicated isExpanded (and toggleExpanded)
for the *current node* (not the tree itself.) The tree component is
the actual bean with these methods that gets called by the value
binding expression. The tree always knows what the "current node" is
because it has access to the model that is being iterrated over.
I have asked Oliver to create a CVS branch. Once he (or someone else)
does this I can submit all of the code. At this point I have enough
code that its worth checking in and having people look at it.
Here we go, I've created the branch, it's called - what a surprise :-)
- new-tree-branch.
Oliver
sean
ps. Have you tried my WAR example yet?
On Tue, 8 Feb 2005 12:29:59 -0600, Heath Borders
<[EMAIL PROTECTED]> wrote:
So, the expanded property for the varNodeToggler will apply to a given
TreeNode object?
I wouldn't think that there would be much need to have the tree either
collapsed or expanded as a whole compared to having individual nodes
expanded or collapsed.
On Tue, 8 Feb 2005 11:06:35 -0500, Sean Schofield
<[EMAIL PROTECTED]> wrote:
who generates the varNodeToggler?
The varNodeToggler is put into request scope by the HtmlTree. In my
implmentation, the varNodeToggler will actually be a reference to the
tree itself. In other words, the HtmlTree will have toggleExpanded
and isExpanded methods. The implementation is shielded from the user
though, they can just take advantage of the request scope variable in
there EL expressions.
-Heath Borders-Wing
sean
--
-Heath Borders-Wing
[EMAIL PROTECTED]
--
Oliver Rossmueller
Software Engineer and IT-Consultant
Hamburg, Germany
http://www.rossmueller.com
