I prefer option #2 where the absence of a binding prefix indicates a
literal, _both_ in templates and specifications.
Informal parameters are always treated as literals, unless otherwise
indicated. Formal parameters should be no different.
#2 is definitely an improvement over #3.
The only purpose for #1 is to save typing time. Unfortunately, I find
that the time saved on typing is eclipsed by the time spent looking up
the default binding prefix values in the component reference (it isn't
always as obvious as the example below).
To avoid this nuisance, I find myself /always/ using a prefix - but is
this not the opposite of this enhancement's intent?
Paul
Howard Lewis Ship wrote:
With the new betas out, I'm thinking that it's become easier to
discuss the binding prefixes.
I like how succinct the prefixes are but if we can get a consensus, we
can change things around.
I would suggest that, if we remove explicit default binding prefixes
on parameters, we still use a simpler system of defaults: literal:
for HTML (or other templates), ognl: for XML and elsewhere (such as
annotations).
<form jwcid="@Form" listener="doSubmit">
vs.
<form jwcid="@Form" listener="listener:doSubmit">
vs.
<form jwcid="@Form" listener="ognl:listeners.doSubmit">
I prefer #1, but would be satisified with #2. Either is better than
#3 (as it stands in Tapestry 3.0).
What are people finding now that they are (hopefully) playing with Tapestry?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
