Tapestry Wish List

[Jeremy Kassis <jk...@jkassis.com>]

I. Simplify the Component Specification Property Binding Syntax

in a .html page template, i use this syntax...
 for ognl bindings:
 <span jwcid="someID@SomeComponent"
someParameterName="ognl:someOgnlExpression" />

 and this syntax for message bindings:
 <span jwcid="someID@SomeComponent " someParameterName
="message:someMessage" />


while in a .jwc (components) or .page (page) specification, i use this
syntax...
 for ognl bindings:
  <component id="someID" type="SomeComponent">
     <binding name="value" expression="someProperty"/>
  </component>
  
 and this syntax for message bindings:
  <component id=" someID " type=" SomeComponent ">
     <message-binding name="value" key="someProperty"/>
  </component>


and i have a <static-binding> tag and an <inherited-binding> tag!  WHEW! All
those different xml tags for something as simple as a parameter binding! Why
not just simplify the syntax? Try.

  <component id="headingInsert" type="Insert">
     <bind param="someParam" to="{type}:someValue"/>
  </component>

              OR

  <component id="headingInsert" type="Insert">
     <bind param="someParam" to="someValue" type="{type}"/>
  </component>

where {type} can be "ognl" | "literal" | "message" | "param"

i'm a real fan of "pretty" xml. and i'm sure i'm not the only one.







II. Support OGNL, message, static, and parameter expressions in the
setInitialValue attribute of the <property-specification> tag

<property-specification name="allowedRoles" type="java.util.List"
persistent="no" initial-value="{ 'root', 'webuser'
}"></property-specification>
Following the pattern of the <binding> and <message-binding> tags, I'd have
to have a <property-specification> and <message-property-specification>.
This doesn't make sense. Tapestry should standardize on the expression
pattern used in the templates. i.e. initial-value="foo" or
initial-value="ognl:foo" or initial-value="message:foo", etc.




III. Simplify the Component Specification Asset Declaration Syntax
I have a <private-asset> tag, a <context-asset> tag, and an <external-asset>
tag.  Why not.
  <asset name="someName" location="someLocation" type="context"/>

where type can be "context" | "private"




Any support or thoughts?



---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org