Yep, it's one of the differences between Tapestry 4 and Tapestry 5. Because we are building a DOM tree, we can finally do true random access updates to the tree throughout the rendering process. No more faking it using nested writers.
It'll also be possible to do some other tricks, such as pretty print the output, or remove excess spaces (we just have to make sure that xml:space attribute is properly honored). On 8/23/06, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
On 8/14/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Author: hlship > Date: Mon Aug 14 06:37:21 2006 > New Revision: 431345 > > URL: http://svn.apache.org/viewvc?rev=431345&view=rev > Log: > Start of a new MarkupWriter implementation based on constructing a light-weight DOM tree. I really like this commit :) ... it's envisioning -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
