One thing that makes code readable and understandable is consistency. This would introduce a different way of defining component bindings that is inconsistent with the current styles. At least the formal and informal are very similar. But these look like two different languages:
<h1>${thread.title}</h1>
<form jwcid="@Form>
...
</form>I do not look forward to templates that look like:
<h1>${thread.title}</h1>
<form jwcid="@Form>
$message{label}<input jwcid="someInputField">
</form>It's ugly, it's inconsistent, and it's a mishmash of style. I'll say it again: too many ways of doing the same thing leads to ugliness, messiness, and also to confusion.
-1 on this.
Jamie
On May 14, 2005, at 10:37 AM, Jamie Orchard-Hays wrote:
Additionally, this will now allow completely invalid HTML templates. <shudder>
On May 13, 2005, at 4:55 PM, 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
