You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by ta...@jakarta.apache.org on 2005/01/09 16:05:34 UTC

[Jakarta Tapestry Wiki] Updated: WhyNotContexts

   Date: 2005-01-09T07:05:34
   Editor: HowardLewisShip
   Wiki: Jakarta Tapestry Wiki
   Page: WhyNotContexts
   URL: http://wiki.apache.org/jakarta-tapestry/WhyNotContexts

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -170,3 +170,5 @@
 
 Howard, I may try to do it whenever I catch some time 
 and after Tapestry 3.1 has gone to the high gear...
+
+HowardLewisShip: Good luck; I don't see this working. You are  looking for a more Swing like appoach, were you create new components as needed to deal with repeats.  Tapestry's model is to render the same components multiple times. There are a large number of reasons, related to efficiency, pooling and scalability, for keeping the structure of a page stable. Tapestry's one-pass approach is very important for dealing with side effects (such as avoiding multiple database queries) and complexities such as loops-within-loops and the use of Block/RenderBlock to dynamically choose what gets rendered.

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org