I think it would be wise for the author of tree2 to document some of
this, but perhaps those that use the tree and answer these questions
do a better job of maintaining the WIKI:

http://wiki.apache.org/myfaces/Tree2

On 1/9/07, Michael Margozzi <[EMAIL PROTECTED]> wrote:
All,

Threads like these always make me wish that the documentation
of this stuff was better. I think the JDK documentation from
sun should be a guide. Between the JavaDocs and the Tutorials
that Sun provided, you could figure out anything.

Documentation is sorely lacking, and not just on this project.
The Ajax4jsf stuff is also extremely poorly documented :-(
I think the number of emails on these mailing list would decline
sharply if we had good Javadocs, tutorials and FAQs. IMHO.

I know I could benefit from this!
Thank God for these lists or I wouldn't be able to get anything working
:-)

Mike

-----Original Message-----
From: djmacpac [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 09, 2007 8:26 AM
To: [email protected]
Subject: Re: Tree2


OK thx, you have a hint for which keyword i should search?

Andrew Robinson-5 wrote:
>
> Search the archives, I don't have an answer handy, but I know that
> question is very frequently asked.
>
> On 1/9/07, djmacpac <[EMAIL PROTECTED]> wrote:
>>
>> No Sorry :-) When I click a folder in the Tree, how can i access the
>> path in the treebacker? How do I know which node was clicked in the
>> tree? I know it will work with TreeState.getSelectedNode, but i can't

>> use the tree state because it won't work with my LARGE htmltree
>>
>>
>> Andrew Robinson-5 wrote:
>> >
>> > The default tree path in the tree2 code is always indexes.
>> >
>> > A  (0)
>> >  -- B  (0:0)
>> >  -- C  (0:1)
>> >    -- D (0:1:0
>> >
>> > ..etc..
>> >
>> > Was this your question?
>> >
>> > On 1/9/07, djmacpac <[EMAIL PROTECTED]> wrote:
>> >>
>> >> But how can I access the path or id of the selected node?
>> >>
>> >>
>> >> Andrew Robinson-5 wrote:
>> >> >
>> >> > The easiest thing is probably a custom tree state object that
only
>> has
>> >> > one expanded path ever stored in it, and when someone expands
the
>> >> > path, it simply overwrites the currently expanded path with the
new
>> >> > one. The renderer always checks the state to determine which to
>> >> > expand.
>> >> >
>> >> > See the tree state API/source for more information
>> >> >
>> >> > -A
>> >> >
>> >> > On 1/8/07, djmacpac <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >> Hi,
>> >> >> I'm using a Tree2 and it works fine. But now I want that, when
I'm
>> >> >> changing
>> >> >> the directory in the tree, the actual opened tree should be
closed
>> and
>> >> >> only
>> >> >> the clicked tree should be opened. normally all tree stay
opened.
>> hope
>> >> >> you
>> >> >> understand what i want to do.
>> >> >> for example:
>> >> >> I ' m browsing up to following path: 0:1:2:3
>> >> >> Now I clck another directory: 0:2
>> >> >> Now the Tree 0:1:2:3 should be closed and only the 0:2 should
be
>> >> >> opened...
>> >> >>
>> >> >> Can anybody help me?

Reply via email to