Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-29 Thread Eelco Hillenius
On 7/29/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > it is already in 1.2 branch if you want to play with it thanks to eelco's > valiant efforts And Matej's efforts to fix it all up again :) It's in wicket-extensions for 1.2, and in 2.0 it replaces the core tree. I made a note in that in the pa

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-29 Thread Igor Vaynberg
it is already in 1.2 branch if you want to play with it thanks to eelco's valiant efforts-IgorOn 7/27/06, michal petras < [EMAIL PROTECTED]> wrote:That's great. Do you know when wiil it be ported to 1.2.1? It could reallyhelp me.--View this message in context: http://www.nabble.com/wicket.markup.h

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-28 Thread michal petras
That's great. Do you know when wiil it be ported to 1.2.1? It could really help me. -- View this message in context: http://www.nabble.com/wicket.markup.html.tree.Tree-is-not-suitable-for-very-big-tree-tf1978583.html#a5520367 Sent from the Wicket - User forum at Nabble.com. ---

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-24 Thread Rice Yeh
Sounds great!On 7/24/06, Matej Knopp <[EMAIL PROTECTED]> wrote: I've just finished new (ajax based) tree (version for wicket 2.0 is insvn (/svnroot/wicket/trunk/wicket-sandbox/users/matej_k/tree) )It's about to be ported to wicket 1.2 and it will likely be a part ofwicket-extensions. It might help

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-24 Thread Matej Knopp
I've just finished new (ajax based) tree (version for wicket 2.0 is in svn (/svnroot/wicket/trunk/wicket-sandbox/users/matej_k/tree) ) It's about to be ported to wicket 1.2 and it will likely be a part of wicket-extensions. It might help you because it works with TreeNode and not DefaultMutable

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-23 Thread David Leangen
> Could you give me more detailed information on what methods in Tree > I should override? > There may be other/better ways, but what I did was this: class MyTree extends Tree { private TreeModelProvider m_provider; ... @Override protected void junctionLinkClicked( DefaultMutableTre

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-21 Thread Rice Yeh
Hi Dave,   Could you give me more detailed information on what methods in Tree I should override? Regards, RiceOn 7/21/06, David Leangen <[EMAIL PROTECTED]> wrote: As an additional note:Actually, I needed to load the data one level lower than what wasdisplayed, otherwise the junction images (with

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-20 Thread David Leangen
As an additional note: Actually, I needed to load the data one level lower than what was displayed, otherwise the junction images (with the + signs) were not displayed correctly. Cheers, Dave On Fri, 2006-07-21 at 15:50 +0900, David Leangen wrote: > I also have a very big tree, and it works

Re: [Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-20 Thread David Leangen
I also have a very big tree, and it works just fine. The secret is to load only the data that is displayed. You need to override the Tree class (it is made for this) and implement it so that only the required data is loaded. Good luck! On Fri, 2006-07-21 at 13:46 +0800, Rice Yeh wrote: > Hi

[Wicket-user] wicket.markup.html.tree.Tree is not suitable for very big tree

2006-07-20 Thread Rice Yeh
Hi,  I find that the implementation of Wicket.markup.html.tree.Tree is not suitable for big tree. It seems because it depends on javax.swing.tree.DefaultMutableTreeNode too much, which asks for populating the whole tree before rendering Wicket.markup.html.tree.Tree. For my case, the tree is very b