> What hacking is required with Data::FormValidator. You can specify a > regexp to define your form fields. But it is not required that all the sets be filled in -- the hacking isn't with D::FV, it's with the data passed to it and the input profile. If I'm displaying 3 subforms, I have to break that data up into three chunks and evalute each subform separately, then look at those results and make a decision. D::FV wants to evaluate the form as a whole, so I either break up my data, or I create a monstrous input profile. I know this sounds unnecessarily complex, but it's come up for 3 different projects already, so I was eager to see if anyone else had solved the problem. > Is this what you are looking for? Or am I missing your original > question completely? I think you've got the right idea, you just missed that a subform isn't required, but the restrictions are required if any part of the subform is completed. (D::FV allows this, but not within the _regexp parameters that would make it easy). > As for the ugly look of the template, I don't think it is that bad, > but that is a personal opinion. I think you are going to be stuck It's not bad .. for a programmer. Turning this over to a designer invites problems. I'm blessed with a good (read: doesn't panic or fiddle) designer for now, but I don't know if that will last. > you want to do some nasty JavaScript hacks to submit your data in nice > ordered chunks, but that just sounds evil to me... Complete agreement. -- SwiftOne suppressed --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.