200 fields on one page! There's this neat concept called "multi-page wizard ..." :->
The IValidationDelegate interface was designed with this kind of thing in mind; you can override it and perform special cases based on element name or component. Before I beefed up validation delegate in about 1.0.8, this would have been more reasonable. Now, though, with the delegate tracking error messages and such for everything ... its a whole can o' worms to allow some fields to have thier own validation delegate; it makes your app more complicated because you have to track in multiple places whether there are errors or not. Let me stew on this a bit longer, or add a feature request and hash it out there. -- [EMAIL PROTECTED] http://tapestry.sf.net > Hi, > > I'm wondering if it would make sense to be able to override the validation > delegate on a per field basis? Somewhere along the way the validation delegate > was moved from ValidField to the Form which simplified things somewhat. But now > I have some fields (on one page out of about 200!) that need to have their > errors handled differently from their form. I am wondering if the delegate > parameter could be put back in the ValidField component, but optional this time > - if not specified then use the form's delegate. Or might there be another way > to use a different delegate for some fields? > > Any thoughts? > > Richard ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
