-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I'll look at it - with the original intent of the component being to cut down on OGNL resolution I can see the benefit, but perhaps there's another way to get the same benefit without the restrictions.
Jesse Kuhnert wrote: > Sure, > > If people think they can find a need for it. I'd like to see it re-written > for tapestry 4.0 though...Possibly even extending the existing If component? > > > What do you think? > > On 3/25/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > Patrick Casey has submitted (20 Nov 05) a Switch/Case component that > looks to address conditionals in a way other than @Conditional and > @Choose. > > I was curious to know thoughts of others in including this in Contrib. > Issue and component code here: > https://issues.apache.org/jira/browse/TAPESTRY-766 >> - --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] >> >> > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://opennotion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEJ1zIaCoPKRow/gARAg8JAJ4233zpvfgcnExePWT9cpMo2daKMgCgtvC4 yflUANnxdVI88XTw69lqL4E= =TsFo -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
