[
https://issues.apache.org/jira/browse/TAPESTRY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534693
]
Christian E Gruber commented on TAPESTRY-1830:
----------------------------------------------
Oh, and using this should include the namespace in the variable declaration, I
should think, so you can ensure that one CAN use the page class if necessary.
Either
<t:loop source="anIterable" value="local:myValue>
<p>${local:myValue}</p>
</t:loop>
or, allow the current syntax to be assumed in the local scope, and make someone
do this to access the page class variable.
<t:loop source="anIterable" value="page:myValue>
<p>${page:myValue}</p>
</t:loop>
I like the former rather than the latter, because most access to variables
without explicit namespace implies the page class, and that should be kept
consistent, I think.
> sharing value and index parameter in loop, count ... compoentes
> ------------------------------------------------------------------
>
> Key: TAPESTRY-1830
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1830
> Project: Tapestry
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: M. H. Shamsi
> Fix For: 5.0.6
>
>
> index and value parameter in loop (and all components like it) often used
> just in page templates and there is no need to access or change them in page
> class.
> sharing this parameters to use directly in page templates, may help
> developers to write most cleaner page classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
