Thanks Ron but i'm not sure that a graphical tree is the best solution
for my users.
The number of categories that we manage is quite big and i'm afraid that
the user get a bit lost ...
I would have prefer dependent dropdown boxes ...
I've tried to implement this without recursivity using a @Fo
do you know tacos?
there is a tree implementation there, initially created by victor - its
very simple yet very powerfull.
Here is the base idee:
--
public abstract class Tree extends AbstractComponent{
@Parameter(required=t
I try to implement a component to let a user choose a category in a tree.
So, i would like to show him at each level of the tree the subcategories
in a combobox.
My problem is that i don't know at compile time the depth of the tree.
That's why i thought that each node of the tree of categories
AFAIK this can not be done directly, but there are solutions for
different problems like displaying a tree using recursion on the model
level - what exactly are you trying to achieve?
Cheers,
Ron
Stephane Decleire wrote:
Hi,
I wonder if there is a way for a tapestry component to include its
Hi Stephane!
I've tried but I've never succeed, but to me there seems that tapestry has
this limitation. I think you can use a trick using the Block / RenderBlock
components , but not totally sure this will work.
hope this helps,
r.
On 1/8/07, Stephane Decleire <[EMAIL PROTECTED]> wrote
Hi,
I wonder if there is a way for a tapestry component to include itself
(in a recursive way).
Despite I have in my template a condition to exit from this infinite
loop, it ends up in a stack overflow error.
I suppose tapestry goes in an infinite loop when it tries to instanciate
the componen
