Re: Re: Re: Re: New Module Consideration?

Completly unrelatedly, what I really think the world needs is a form validation module that will both validate the form after it's submitted for security, and generate JS to validate the form before submittion to be nice for the user.

Actually, what the world needs is less of these CGI.pm-style modules that try and do too much at once. Separate tasks, like generating javascript and doing server-side validation, should be in separate modules. Going the other way results in reduced reusability in the components and does nothing to solve the problem.

But that's just another anonymous monk's opinion.

Comment on Re: Re: Re: Re: New Module Consideration?

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: New Module Consideration? by Anonymous Monk on Jan 26, 2003 at 03:09 UTC
As for: and generate JS to validate the form before submittion to be nice for the user. Keep in mind it's very nice to the server as well. I don't have stats on it (would it matter if I did?) but I'm betting client-side validation would at least cut requests for the script in half.	[reply]
Re^6: New Module Consideration? by Aristotle (Chancellor) on Jan 26, 2003 at 05:17 UTC
Even so, the point still stands. If you really need autogenerated validation Javascript, it should be implemented in a separate module. Maybe it should have an interface to the data validator module, so that it could generate JS according to a validator object's rules, but it should not be intermingled in the validator module's codebase and interface. Makeshifts last the longest.	[reply]