> anyway? If the loop can already figure these out, make them read-only
> properties of the loop. Then you could reference them like ${loop_id.index}
> or ${loop_id.value}.
>
That'd be nice in some cases, but there are also times when I want to
be able to access them through my component class. I like being able
to separate out my rendering logic from my page so that I could change
it in one place. For instance, if you want to color rows of a table
its nice to be able to do something like
<tr class="${rowClass}">...</tr>
and let the component decide the row colouring scheme based on the
rows position. I suppose you could access the Loop component directly
to ask it it's position when getRowClass() is called. This leaves you
with a pretty clean template, I suppose potentially at the expense of
the class file...
Josh
--
--
TheDailyTube.com. Sign up and get the best new videos on the internet
delivered fresh to your inbox.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
