That is a good idea! That will keep me from messing with the extra
storage and I won't have to go to two different places for parent child
relationships. I was hoping there was something already created for
what I am trying to do that would make the process easier. I appreciate
your help! T
If your domain objects have a reference to their parents, why bother
with the component structure?
You can walk up your domain tree to search the 'previous' one. All you
have to do, is re-applying the ordering when you iterate over the children.
Sven
On 11/02/2012 08:08 PM, Jered Myers wrote
The domain objects do know the parent, but they do not know what order
they exist within their siblings.
Usecase:
- I have a tree of departments that has a list of employees in the tree
where the parent node is the department and the child nodes are employees.
- The tree is handling navigation
I see, you've been using part of Swing's API to traverse the tree.
Don't your domain objects of the tree know their parents? If not, you
may be able to walk up the Wicket component tree to the parental tree
item to get the parent domain object.
What do you use this for? What's your usecase?
I am still using the deprecated tree and am building the new tree in a
sandbox, so I am able to put the update on hold if there is a good
solution on the way in the next few weeks. We are attempting to move to
the new tree so that we are not having to scramble once the deprecated
methods are r
Hi,
when do you need this information? How did you do it in 1.5?
Sven
On 11/01/2012 10:34 PM, Jered Myers wrote:
I am updating my trees from Wicket 1.5 to 6.2. I need to get the next
node and previous node related to the node the user has selected. I
am using a NestedTree similar to http://
