It's desperately in need of refactoring to extend off of
the new TreeRenderer, and not the old 'uix' one.
-- Adam
On 10/8/07, Cristi Toth [EMAIL PROTECTED] wrote:
Hi all!
I need I really need the navigationTree and I noticed the renderer is still
in the 'uix' package
and that the code
Hi Adam!
No problem, I'll do it.
But I need to know some start points...
i.e. It took me some 1/2 hour to figure that the actual renderer that does
the job
is the NavigationTreeRenderer from ui.laf.desktop package not the close to
useless one from the uix package.
Is something from the uix
Ah, OK, I see the confusion.
The renderer in uix handles the decoding side of things.
The renderer in uinode handles just the rendering thing,
'cause it's from an old architecture that didn't have any
built-in decoding.
Ideally, we'd have one new renderer in core.xhtml that
extends TreeRenderer
