[
https://issues.apache.org/jira/browse/TAPESTRY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534740
]
Nick Westgate commented on TAPESTRY-1830:
-----------------------------------------
I was thinking along the lines of an OGNL expression passing in the component
name, but this would still require exposing the component resources as a
property and fishing around in there (which is what the component binding is
shorthand for).
Not only would this make the OGNL expression verbose, I think Howard might
label it a Bad Thing. ;-)
Your component binding suggestion is interesting if we view it as "chaining"
different bindings, with default chain of prop.
And I don't want to start an edit war ;-) but I removed the duplicate and T5
affects from TAPESTRY-1694.
Devs need one JIRA per issue (per framework) to close. Duplicate is used for
closing redundant issues.
If you change your comment to mention this issue it will be linkage enough
between the two.
Cheers,
Nick.
> 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]
