Matt, I actually used both and they behave exactly the same way. Both at
the very end use a TreeModel. The navigationTree wants a MenuModel,
which usually is just a wrapper around a TreeModel.
I admit I set getFocusRowKey() just returning null, but the entire topic
concerning the focus is obscure to me. Documentation exaplains it as a
kind of selection, but normal selection is managed anyway on both
components (together with action/event), so I don't understand the
difference.
Selection bolding depends on style selectors, indeed mine behave the
same way (I feel they even use the same selectors, p_OraTreeRow,
OraLinkDisabled, etc).
-- Renzo
Matt Cooper wrote:
The navigationTree supports a concept of a focus path (focus row key)
which
could be used to identify a position into the navigation hierarchy
(e.g. by
bolding the tree nodes along the focus path). I believe the tree
component
doesn't share this added specialty.
Regards,
Matt
On 2/8/07, Renzo Tomaselli <[EMAIL PROTECTED]> wrote:
Hi all, I successfully used tr:tree for representing tree-shaped data
structures.
Now I need a hierarchical menu (to replace Tomahawk t:panelNavigation2),
thus I'm a bit confused between tree and navigationTree.
Basically, using a tree would satisfy navigation requirements.
Why using navigationTree instead ?
Is anybody able to shortly englight the rationale behind this choice ?
Thanks -- Renzo
