hi,
the Loop component is used basically used by (define a list t:source and
bind a local iterable var t:value to access the values later):
...
<ol t:type="loop" t:source="listItems" t:value="listItem">
<li>${listItem.name}</li>
</ol>
...
What I find a bit clumsy is that you have to put this local-variable
also to your page class:
Page{
List<Item> listItems;
Item listItem;
...
//getter+setters
}
Why is tapestry not holding/creating the listItem local-var on the fly
itself, instead of forcing to create a duplicated local variable
(listItem is derived from listItems) inside the page class?
--
manuel aldana
ald...@gmx.de
software-engineering blog: http://www.aldana-online.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
