[
https://issues.apache.org/jira/browse/TAPESTRY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534723
]
Christian E Gruber commented on TAPESTRY-1830:
----------------------------------------------
Hmm. True, but Howard's suggestion still requires that something be coded into
the page class. (ie, the loop component itself). I'd like to see no
requirement for that for purely "internal" local variables.
when you say "can access the component", are you meaning something like
${component:<comp_id>:<variable>} ?
> allow local value and index parameters (i.e. not page class variables) in
> loop, count ... components
> ----------------------------------------------------------------------------------------------------
>
> 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]
