You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Apache Wiki <wi...@apache.org> on 2011/01/02 01:54:54 UTC

[Tapestry Wiki] Trivial Update of "ImprovedValidationProposal" by BobHarner

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.

The "ImprovedValidationProposal" page has been changed by BobHarner.
The comment on this change is: outdated note.
http://wiki.apache.org/tapestry/ImprovedValidationProposal?action=diff&rev1=2&rev2=3

--------------------------------------------------

+ || NOTE: This information applies to an older version of Tapestry.  For current information see [[http://tapestry.apache.org/input-validation.html]]. ||
+ 
  = Problem Description =
  
  Tapestry's validation subsystem is quite powerful, but has evolved over time in fits and starts. The Tapestry 3.0 implementation is powerful and flexible, but could be ''simpler'' and more ''consistent''.
@@ -51, +53 @@

  
  How would a validaiton delegate decorate a non-text field, such as a check box or drop down list?  How can the validation delegate determine the "flavor" of component it is decorating (i.e., is it a traditional text field, a drop down list, a check box, a text area, etc.).  This may involve some significant API changes.  Possibly, IFormComponent would need an additional method for this purpose.
  
- 
- 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org