This is the approach I take ... use the Java code to massage the data
from the shape that makes sense for external storage (or whatever the
API is), into the shape that make sense for rendering.
It helps that you can just use inner classes of your page/component
class, with public fields, so it's not a lot of work.
On Mon, Oct 8, 2012 at 8:54 AM, Lance Java <lance.j...@googlemail.com> wrote:
> Nabble ate my post:
>
> So, you could write a getter like this:
>
> public List<List<Asset>> getGrid() {
> ...
> }
>
> Then your TML could look something like
>
> [table]
> [t:loop source="grid" value="row"]
> [tr]
> [t:loop source="row" value="asset"]
> [td][img src="${asset}" /][/td]
> [/t:loop]
> [/tr]
> [/t:loop]
> [/table]
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/first-flag-variable-for-request-cycle-loop-tp5716705p5716709.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
