I think OGNL will be very cool, mostly because a lot of
mundane logic can shift into the specification.
For example:
<component id="insertAmount" type="Insert">
<binding name="value" ...
<binding name="class" expression="classForAmount"/>
</component>
public String getClassForAmount()
{
return getAmount() > 90 ? "warning" : "normal";
}
We can now get rid of the method and put that logic
right into the binding:
<binding name="class" expression='amount >
90 ? "warning" : "normal"'/>
Thanks again for the great work and leadership. I'm
busy linking JavaDoc pages to the component reference
and double checking everything.
--
[EMAIL PROTECTED]
http://tapestry.sf.net
> Hi Howard and Neil,
>
> I have complete the Component Reference checkin. This includes replacing
> all the "property-path" bindings with "expression".
>
> This should be good to go for the 2.2 Beta, after some quality checks.
>
> I had a look at the OGNL today, looks like a very good move. Also Ant 1.5 is
> great, it screams along doing documentation builds.
>
> thanks for your help
>
> Regards Malcolm
>
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos:
> http://photos.msn.com/support/worldwide.aspx
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer
