tapestry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From conflue...@apache.org
Subject [CONF] Apache Tapestry > Release Notes 5.3.0
Date Wed, 30 Mar 2011 16:34:00 GMT
<html>
<head>
    <base href="https://cwiki.apache.org/confluence">
            <link rel="stylesheet" href="/confluence/s/2042/9/12/_/styles/combined.css?spaceKey=TAPESTRY&amp;forWysiwyg=true"
type="text/css">
    </head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Notes+5.3.0">Release
Notes 5.3.0</a></h2>
    <h4>Page <b>edited</b> by             <a href="https://cwiki.apache.org/confluence/display/~hlship">Howard
M. Lewis Ship</a>
    </h4>
        <br/>
                         <h4>Changes (1)</h4>
                                 
    
<div id="page-diffs">
                    <table class="diff" cellpadding="0" cellspacing="0">
    
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >It is now possible to have Tapestry
emit rendering comments; these are comments (such as {{&lt;!\-\-BEGIN Index:loop (context:Index.tml,
line 15)\-\-&gt;}}) that can assist you in debugging markup output on the client-side.
This is enabled for all requests using the configuration symbol {{tapestry.component-render-tracing-enabled}},
and can be added to any request by adding the query parameter {{t:component-trace=true}} to
the URL. This will significantly increase the size of the rendered markup, but can be very
helpful with complex layouts to determine which component was responsible for which portion
of the rendered page. <br> <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">When
making contributions to a service, you are no longer restricted to contributing a value that
is assignable to the type associated with the configuration; objects of any type may be contributed,
and the TypeCoercer service is used to coerce the value to the configuration&#39;s type.
<br> <br>Because of how Tapestry instruments your pages and components, it has
been difficult to debug Tapestry applications; any mutable field shows its default value in
the debugger, regardless of what has been written to the field or read out of it. In Tapestry
5.3, when in _development mode_, Tapestry now shadows values read from or written to such
fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance release).
This does not occur in production, to avoid potential memory leaks. <br> <br></td></tr>
            <tr><td class="diff-unchanged" >{scrollbar} <br></td></tr>
    
            </table>
    </div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">
        <style type='text/css'>/*<![CDATA[*/
table.ScrollbarTable  {border: none;padding: 3px;width: 100%;padding: 3px;margin: 0px;background-color:
#f0f0f0}
table.ScrollbarTable td.ScrollbarPrevIcon {text-align: center;width: 16px;border: none;}
table.ScrollbarTable td.ScrollbarPrevName {text-align: left;border: none;}
table.ScrollbarTable td.ScrollbarParent {text-align: center;border: none;}
table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width: 16px;border: none;}

/*]]>*/</style><div class="Scrollbar"><table class='ScrollbarTable'><tr><td
class='ScrollbarPrevIcon'><a href="/confluence/display/TAPESTRY/Release+Notes+5.2.5"><img
border='0' align='middle' src='/confluence/images/icons/back_16.gif' width='16' height='16'></a></td><td
width='33%' class='ScrollbarPrevName'><a href="/confluence/display/TAPESTRY/Release+Notes+5.2.5">Release
Notes 5.2.5</a>&nbsp;</td><td width='33%' class='ScrollbarParent'><sup><a
href="/confluence/display/TAPESTRY/Release+Notes"><img border='0' align='middle' src='/confluence/images/icons/up_16.gif'
width='8' height='8'></a></sup><a href="/confluence/display/TAPESTRY/Release+Notes">Release
Notes</a></td><td width='33%' class='ScrollbarNextName'>&nbsp;</td></tr></table></div>

<p>It is now possible to have Tapestry emit rendering comments; these are comments (such
as <tt>&lt;!&#45;&#45;BEGIN Index:loop (context:Index.tml, line 15)&#45;&#45;&gt;</tt>)
that can assist you in debugging markup output on the client-side. This is enabled for all
requests using the configuration symbol <tt>tapestry.component-render-tracing-enabled</tt>,
and can be added to any request by adding the query parameter <tt>t:component-trace=true</tt>
to the URL. This will significantly increase the size of the rendered markup, but can be very
helpful with complex layouts to determine which component was responsible for which portion
of the rendered page.</p>

<p>When making contributions to a service, you are no longer restricted to contributing
a value that is assignable to the type associated with the configuration; objects of any type
may be contributed, and the TypeCoercer service is used to coerce the value to the configuration's
type.</p>

<p>Because of how Tapestry instruments your pages and components, it has been difficult
to debug Tapestry applications; any mutable field shows its default value in the debugger,
regardless of what has been written to the field or read out of it. In Tapestry 5.3, when
in <em>development mode</em>, Tapestry now shadows values read from or written
to such fields into the fields themselves (this has also been fixed in the 5.2.5 maintenance
release). This does not occur in production, to avoid potential memory leaks.</p>

<style type='text/css'>/*<![CDATA[*/
table.ScrollbarTable  {border: none;padding: 3px;width: 100%;padding: 3px;margin: 0px;background-color:
#f0f0f0}
table.ScrollbarTable td.ScrollbarPrevIcon {text-align: center;width: 16px;border: none;}
table.ScrollbarTable td.ScrollbarPrevName {text-align: left;border: none;}
table.ScrollbarTable td.ScrollbarParent {text-align: center;border: none;}
table.ScrollbarTable td.ScrollbarNextName {text-align: right;border: none;}
table.ScrollbarTable td.ScrollbarNextIcon {text-align: center;width: 16px;border: none;}

/*]]>*/</style><div class="Scrollbar"><table class='ScrollbarTable'><tr><td
class='ScrollbarPrevIcon'><a href="/confluence/display/TAPESTRY/Release+Notes+5.2.5"><img
border='0' align='middle' src='/confluence/images/icons/back_16.gif' width='16' height='16'></a></td><td
width='33%' class='ScrollbarPrevName'><a href="/confluence/display/TAPESTRY/Release+Notes+5.2.5">Release
Notes 5.2.5</a>&nbsp;</td><td width='33%' class='ScrollbarParent'><sup><a
href="/confluence/display/TAPESTRY/Release+Notes"><img border='0' align='middle' src='/confluence/images/icons/up_16.gif'
width='8' height='8'></a></sup><a href="/confluence/display/TAPESTRY/Release+Notes">Release
Notes</a></td><td width='33%' class='ScrollbarNextName'>&nbsp;</td></tr></table></div>
    </div>
        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href="https://cwiki.apache.org/confluence/users/viewnotifications.action"
class="grey">Change Notification Preferences</a>
        </div>
        <a href="https://cwiki.apache.org/confluence/display/TAPESTRY/Release+Notes+5.3.0">View
Online</a>
        |
        <a href="https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=24190989&revisedVersion=6&originalVersion=5">View
Changes</a>
            </div>
</div>
</div>
</div>
</div>
</body>
</html>

Mime
View raw message