I think this issue is a moot point. But I will say that the tree
example is a perfect example because of it's nature.
> Any tree can be easily walked through like a list,
> but then rendered (indented) to look like a tree to the user.
Of course it can. That's not really the point. The point is tha
I can't really see why is not having recursive components
such a problem.
Any tree can be easily walked through like a list,
but then rendered (indented) to look like a tree to the user.
So, rendering recursive data, like BeanEditForm should be
no science fiction. Like any other thing, providing
Hello Todd,
Todd Orr wrote:
I'm also trying to perform this type of recursive structure. I don't
agree that this makes anything simpler. Recursion is a powerful and
concise tool for these situations. I will say that it is often abused,
but this is a perfect use case. A recursive solution to this
H de Paula Figueiredo [mailto:[EMAIL PROTECTED]
Sent: Tue 8/21/2007 10:52 AM
To: Tapestry users
Subject: Re: Recursion of components
On Tue, 21 Aug 2007 12:54:05 -0300, César Les <[EMAIL PROTECTED]> wrote:
> maybe Tapestry should support alternatives to components like Rails do
> with
On Tue, 21 Aug 2007 12:54:05 -0300, César Les <[EMAIL PROTECTED]> wrote:
maybe Tapestry should support alternatives to components like Rails do
with Partial Templates. So whe can choose the right tool for the right
job.
As far as I know, you don't really need to *instantiate* components on the
ckBerry by AT&T
-Original Message-
From: "César Les" <[EMAIL PROTECTED]>
Date: Tue, 21 Aug 2007 10:54:05
To:"Tapestry users"
Subject: Re: Recursion of components
maybe Tapestry should support alternatives to components like Rails do
with Partial Templates. So wh
maybe Tapestry should support alternatives to components like Rails do
with Partial Templates. So whe can choose the right tool for the right
job.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
> >putting one loop inside another freaks Tapestry out. This is just dumb.
> I absolutely agree if this is true, in T4 I used nested loops without
> issues though?
Yes. Nested loops do work fine in tapestry. I was not being as
specific as I should have been. As loops are iterative they work fine.
Nested loops work fine in T5 of course. I believe he is describing recursion.
Cheers,
Nick.
Peter Stavrinides wrote:
Hi Todd
Interesting comments, particularly this:
>putting one loop inside another freaks Tapestry out. This is just dumb.
I absolutely agree if this is true, in T4 I used nest
Hi Todd
Interesting comments, particularly this:
>putting one loop inside another freaks Tapestry out. This is just dumb.
I absolutely agree if this is true, in T4 I used nested loops without
issues though?
For more complex components like the grid component I disagree though,
even the larges
What's worth considering is that the reason it exists at all is
purely an implementation detail. There is already a pseudo-dynamic
component creating ability in Tapestry. Consider a Loop component that
contains other components. Somehow, Tapestry, in this case, knows what
to generate at runtime si
As Howard has authored - it is Principle 1 of tapestry - see
http://tapestry.apache.org/tapestry5/ towards the bottom of the page.
Richard.
Nick Westgate wrote:
There's been plenty of discussion about this in the past, and using
blocks from a template is the usual solution, eg:
http://www.behi
There's been plenty of discussion about this in the past, and using
blocks from a template is the usual solution, eg:
http://www.behindthesite.com/blog/C1931765677/E923478269/index.html
I believe the "static structure, dynamic behaviour" mantra is for the
sake of performance, and a fundamental fr
Interesting, I hit this same wall a while ago when trying to render a
tree. It seems to be a common occurrence, so supporting it in the
framework would be highly desirable. I ended up doing almost all the
rendering in Java code, using the template only to hold blocks which I
called to render from
I couldn't believe it, so I made an example. And I had to discover that
it is true:
org.apache.tapestry.ioc.internal.util.TapestryException
The template for component example.recursive.components.Node is
recursive (contains another direct or indirect reference to component
example.recursive.compon
I'm also trying to perform this type of recursive structure. I don't
agree that this makes anything simpler. Recursion is a powerful and
concise tool for these situations. I will say that it is often abused,
but this is a perfect use case. A recursive solution to this problem
is far simpler and may
Dmitry Sidorenko wrote:
Hi all.
Hi,
In my project I need to generate edit form for a class like this:
class Section{
List subSectionList;
List fieldList;
}
> [...]
Probably I'm doing something wrong, maybe my task should be done in
completely different manner.. Any ideas?
Is there any
17 matches
Mail list logo