You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Christian E Gruber (JIRA)" <de...@tapestry.apache.org> on 2007/10/15 00:17:50 UTC

[jira] Commented: (TAPESTRY-1830) sharing value and index parameter in loop, count ... compoentes

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

Christian E Gruber commented on TAPESTRY-1830:
----------------------------------------------

There needs to be a namespace in the ${} notation for this sort of thing, unless we're going to go with some sort of cascading resolution, which I expect would have a negative performance impact if used, say, in loops a lot.  ${temp:foo} was suggested on the list.  ${local:foo} might be another.  

I was originally thinking of ${component:foo} but the problem is there's arbitrary nesting of components below the loop or other containing component, so there's no guarantee that you're hitting the right one.  Having a page-level scratch namespace would requrie that people name variables to avoid collision (which they have to do now anyway) but keep it simple, and (probably) way easier to implement and make fast.

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