I don't much like this idea (-1). I agree that we don't need yet another way of declaring a component in a template, especially one that is completely different to the existing templating syntax. What happened to "less is more"? This feels like "more is less" to me :-(

Richard

Howard M. Lewis Ship (JIRA) wrote:
Simplified insert binding template syntax
-----------------------------------------

Key: TAPESTRY-331
URL: http://issues.apache.org/jira/browse/TAPESTRY-331
Project: Tapestry
Type: New Feature
Components: Framework Versions: 4.0 Reporter: Howard M. Lewis Ship
Priority: Minor
Fix For: 4.0



It would be desirable to support a simplified syntax for obtaining data via bindings and inserting it. A proposal has been to adopt ant-like syntax ("${...}") and interpret the expression within the braces as a binding reference. This would eliminate the need for many Insert components, i.e.:


<h1>${thread.title}</h1>

rather than:

<h1><span jwcid="@Insert" value="thread.title"/></h1>

Or:

${message:prompt}

rather than:

<span key="prompt"/>


This kind of substitution is less invisible, but generally less intrusive, than creating a new component.

Further, the use of the Any component could be reduced via support for:

<img src="${imagePath}"/>

rather than:

<img jwcid="@Any" src="ognl:imagePath"/>


Some questions occur; are the following legal?

<${element}> ... </${element}>
<img jwcid="@Image" src="${asset:foo}"/>
<div ${attribute}="${value}"/>


A final note: these bindings should be treated as we treat informal parameters today; this includes automatically expanding IAssets into their corresponding URLs.


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to