You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <de...@tapestry.apache.org> on 2007/12/22 17:12:49 UTC
[jira] Updated: (TAPESTRY-1623) Access to block parameters
[ https://issues.apache.org/jira/browse/TAPESTRY-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAPESTRY-1623:
-------------------------------------------
Fix Version/s: (was: 5.0.7)
5.0.8
> Access to block parameters
> --------------------------
>
> Key: TAPESTRY-1623
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1623
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.0.5
> Reporter: Dan Adams
> Fix For: 5.0.8
>
>
> One of the features I used in T4 which made it very powerful was the ability to pass informal parameters to a Block and then get them from within the block. BeanEditForm demonstrates making a context available to blocks via an environmental interface but this seems like too much overhead for less formally defined situations. Perhaps it could look something like this:
> <t:delegate to="block:myblock" foo="bar" />
> <t:block id="myblock">
> ${context.parameters.bar}
> </t:block>
> in the class:
> @Environment
> private BlockContext context;
> the interface:
> public interface BlockContext {
> Map<String, Object> getParameters();
> }
> This would also required being able to do more OGNL-like expressions.
--
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