tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Commented: (TAPESTRY-1830) allow local value and index parameters (i.e. not page class variables) in loop, count ... components
Date Thu, 03 Jan 2008 20:14:34 GMT

    [ https://issues.apache.org/jira/browse/TAPESTRY-1830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555664#action_12555664

Howard M. Lewis Ship commented on TAPESTRY-1830:

I think this could be done.  We could have a Map associated with each component, used to store
these kinds of values.  A "var:" binding prefix (I prefer that the "local:") would read and
update the Map.  The Map would be cleared after the component finished rendering.

Because there is no type information in a Map value, we really couldn't do much with a property
expression (which is based on type safe signatures).  But still, a lot of simple cases (such
as the looping output above) could be accomplished.

Again, if you are doing anything complicated, you would want to define a component property
to hold the value, which nails the type, making it possible to use property expressions. 
But if you just need to hold the value and pass it as a parameter elsewhere, this would work

> 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
> 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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message