For the moment, you can use the negate parameter of the If component.
I would eventually like to convert the prop: expression language from ad-hoc into something more formal, based on a real grammar. I don't think I ever want it to be as sophisticated as OGNL, but it would be nice if it could handle access to Map properties or List or array indices. The major purpose of T5's property expressions is that along with the type safety, we can resolve down to a particular getter/setter method and find the annotations, and that drives a lot of smart default logic (it's the way that TextField and friends can automatically deduce validations based on property annotations). I don't think OGNL will be capable of doing the same. Glad to see you delving into T5, can't wait to see what you come up with! On 6/7/07, Dan Adams <[EMAIL PROTECTED]> wrote:
So I'm jumping into T5 and most of my ognl expressions like "foo.bar.baz" all transfer pretty effortlessly into prop. As for other more complicated expressions like "ognl:foo ? bar : baz" these I can move into a public method. But often I'll have expressions like "ognl:! foo". How do simple expressions like this translate over to T5? Will ognl be supported at all in T5 for situations where I'm willing to pay the expense of a slower expression? -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
