tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 20598] - Using @Conditional within a tag
Date Mon, 09 Jun 2003 20:41:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20598>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20598

Using @Conditional within a tag





------- Additional Comments From rlewisshell@mac.com  2003-06-09 20:41 -------
Actually, for consistency, I was suggesting we add an 'if' parameter to all 
core components, not just Any.  Yes, this makes the conditional almost 
unnecessary, but having more than one way to do the same thing is good.  Maybe 
I've just been using ant too much recently, but the if/unless= attributes are 
pretty handy there.  If all the structural components had a conditional aspect 
it would help simplify component graphs (as the extra level introduced with 
conditionals could be removed).

Regardless, I really like the idea of a component having access to its 
template's element.

Mime
View raw message