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 in core.xhtml. -- Adam On 10/8/07, Cristi Toth <[EMAIL PROTECTED]> wrote: > 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 package classes really needed in this case? > Should I rely on the old ComandNavigationRenderer or refactor that too? > > Please tell from where to start (so I don't loose to much time) > and what things should I look for (not to mess it up). > > I really need this and I have a very short time for this. (wednesday at > noon) > > > On 10/9/07, Adam Winer <[EMAIL PROTECTED]> wrote: > > 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 is... still old style and I don't understand nothing. > > > It's extremely short and I didn't figure it out where's all the > rendering > > > implemented. > > > > > > Can somebody help me with some hints? > > > I would like to refactor it and enhance its skinning (which for now > seems to > > > be disabled) > > > > > > -- > > > Cristi Toth > > > > > > ------------- > > > Codebeat > > > www.codebeat.ro > > > > > > -- > > Cristi Toth > > ------------- > Codebeat > www.codebeat.ro
