Hi guys,
Just as a preface, I'm really not trying to be a pain in the neck --
I'm just trying to make my code as clean and easy as I possibly can.
Dumping default bindings meant my components went from something like:
<component id="email" type="TextField">
<binding name="displayName" value="E-mail Address"/>
<binding name="validators" value="required, email"/>
<binding name="value" value="email"/>
</component>
to:
<component id="email" type="TextField">
<binding name="displayName" value="literal:E-mail Address"/>
<binding name="validators" value="validators:required, email"/>
<binding name="value" value="email"/>
</component>
I'd have to say that I think I actually prefer the different binding
tags in 3.0. I think the following is generally easier to read:
<component id="username" type="ValidField">
<static-binding name="displayName" value="E-mail Address"/>
<binding name="validator" expression="beans.required"/>
<binding name="value" expression="email"/>
</component>
At least in Tapestry 3, values were values and expressions were
expressions.
So, I guess my question is, how much trouble would I be getting
myself into if I tried combining these binding elements into the 4.0
DTD? I really like what Tapestry 4 is doing is general, but this is
looking to be a potential show stopper for me. Once again, I'm not
looking to reopen the default binding can of worms. It seems that
ship has sailed, so now I'm just trying to find the next best thing
without being ridiculously verbose.
Thanks,
Kevin
