Hi Robert:
yes, that's the way that I had be doing, but it should be easier if I
can "push" components and of course I can to push this components
depending on conditions. Right now I have to write a lot of blocks and
worst I cannot re-use some blocks depending on conditions and sumarize
to obtain a bigger block (to do it I suppose that I have to define
inside another renderBlock/Block depending on a condition if renders or
not). But all this work could be avoided if the page's component tree
were dynamic, and the approach -it's my opinion- from the developer's
point of view easier and more "natural".
By the other side, generate dynamic pages could be a performance problem
(I don´t know), then maybe better have the option to generate or
configure if the page is dynamic or static, but have at least the option
and the developer decides what's the better (not only performance,
including maintenance, functionality, etc) option.
Thanks
JQ
Robert Zeigler wrote:
You can, of course, simulate the dynamic component behavior using
block/render block.
Since you can pull your block to be rendered from anywhere (even other
pages), you can define your components components to be added within a
page besides the one that's rendering, and get the effect of dynamic
component addition.
Robert
Patrick Casey wrote:
I think what he's getting at is this:
The way tapestry works today, a page is a static tree of components.
Based on various conditional statements, not every component in the tree
gets built for a specific page render, but they actual set of
components is
fixed at design time.
He'd like to be able to programmatically add a new component to the
page tree at run time.
--- Pat
-----Original Message-----
From: Mark Stang [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 12, 2006 9:06 AM
To: Tapestry users; Tapestry users
Subject: RE: instantiating components directly
Can you be more specific about how you want to "instantiating components
directly". I am just trying to understand the definition. Do you
want to
"draw" a page on the fly? Taking components and re-arranging them on
the
page or on a new page? Or creating components that don't exist at the
start of the server but they do later?
thanks,
Mark
-----Original Message-----
From: Jorge Quiroga [mailto:[EMAIL PROTECTED]
Sent: Thu 1/12/2006 9:58 AM
To: Tapestry users
Subject: Re: instantiating components directly
This issue about dynamic component generation should be considered
seriously for the next major release, because is very necessary and
asked by the community, after all, if almost all are components it
should be possible (if ASP.NET and others can, why not tapestry?).
I'm newbie with T4, and that T4 cannot do it has been very annoying and
for some cases (specially when navigation is defined by state) I have to
choose the less simpler path, and the most simple is one of the claimed
policies in Tapestry, of course T4 isn`t a web panacea, but this is a
really community need.
Thanks.
JQ
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Ing. Jorge Enrique Quiroga
Analista programador
PCT LTDA
Teléfonos: 4800069-4800046-4811984
Dirección: Carrera 28 bis Nº 51-08
Bogota D.C. - Colombia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
