Hi, I noticed that the For and If components are already included in Tapestry 4 in the framework. I believe they're intended as replacements for Foreach and Conditional. As such, I was wondering why not just rename For as Foreach and If as Conditional? Below are the benefits: 1. Existing code doesn't need to be changed to use the new components. 2. It is far easier to search the mailing list archive or web pages using Foreach or Conditional as keywords than For and If (these two words are far too common).
The only drawback that I can think of is that if some people are using Foreach in a form and maintaining the "source" themselves, then their source objects may not be squeezable. When upgrading to this new version of Foreach (For), their code will break. Of course, it should be very rare to use Foreach in a form instead of a ListEdit. Any thought on this? -- Author of an e-Book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
