That looks awesome ... I get constant pushback on the need to define a value property to store the current object.
I would say we could start to deprecate the "var:" binding prefix once this is in place. On Wed, Aug 25, 2010 at 11:50 PM, Josh Canfield <[email protected]> wrote: > I went back over the generics code and added better support for > wildcard and parameterized types. > > One of my favorite parts of this change is the new improved Loop: > > �...@property > �...@component(parameters = {"source=personSource"}) > private Loop<Person> personLoop; > > �...@property > private List<Person> personSource; > > > <h2>Person Loop</h2> > <t:loop t:id="personLoop"> > <div id="person_${personLoop.index}">${personLoop.value.name}</div> > </t:loop> > > I was able to make the value and index properties of loop public and > access them from the template. > > Jira is down right now or I'd file a defect and attach it... I guess > I'll do that later if needed. > > > Josh > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
