RE: [Tapestry-developer] Why doesn't the Conditional comonent not accept informal parameters ?

[Elankath, T. (Cognizant) <ET...@bl...>]

I apologize to the list for my critical post. I didn't mean to be =
offensive or negative.

I was interested in knowing whether there is a particular reason that =
the Conditional components forbids informal parameters.

Thank you,
Tarun





-----Original Message-----
From: Elankath, Tarun (Cognizant) [mailto:ET...@bl...]
Sent: Monday, February 24, 2003 5:43 PM
To: tap...@li...
Subject: [Tapestry-developer] Why doesn't the Conditional comonent not
accept informal parameters ?


Hi list,

I am rather peeved that the conditional component doesn't accept =
informal parameters. I have an element with a CLASS attribute that I =
wish to display conditionally. Unfortunately, if I give a jwcid to this =
element and let it be a conditional component, then the CLASS attribute =
is invalid.

IMHO, this is a bug. I don't see any good reason as to why informal =
parameters are forbidden int the conditional component. As far as good =
sense goes, informal parameters should be allowed in all circumstances =
for all components, it should only be disabled in case of conflict.

I know have to put an un-necessary pair of <span jwcid=3D"ifBlah"> tags =
around the element now.  This only messes the template, instead of =
keeping it inviolate.=20


Regards,
Tarun


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
Tap...@li...
https://lists.sourceforge.net/lists/listinfo/tapestry-developer