Hi
One thing that surprises me about T5 is that I still have to declare methods
in my class for looping.
1. Wouldn't this be more in line with T5's commitment to painless
development to support:
<t:loop source="myCollection">
${current.someProperty}
</t:loop>
In the cases where it is needed (hardly ever in my experience) the "value"
attribute would still enable another property to be used. My classes seem
to be cluttered with loop fields.
2. Regarding the docs
[http://tapestry.apache.org/tapestry5/tapestry-core/ref/org/apache/tapestry5/corelib/components/Loop.html]
The NavBar.java example provides a loop field "_pageName", which is not
marked as a property. Would this field need to be cleared via pageDetach to
avoid state hanging around in the pool?
Richard Hoberman
--
View this message in context:
http://www.nabble.com/-T5--Loops---implicit-value--tp19011764p19011764.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
