in reply to Re: Re: New Module Consideration?
in thread New Module Consideration?

As an example, if you've got a form that says "rank the following ten items from most important (1) to least important (9)", they must sum to 45.

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.

Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).

Replies are listed 'Best First'.
Re: Re: Re: Re: New Module Consideration?
by Flame (Deacon) on Jan 03, 2003 at 20:36 UTC
    Hmm, that's an interesting idea, I'll see if I can think of a way to incorperate it... Thanks


    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS | GMS

[reply]
Re: Re: Re: Re: New Module Consideration?
by Flame (Deacon) on Jan 06, 2003 at 20:16 UTC
    I have the solution to this suggestion. I'm changing the way you select your element to optionally be an array ref. eg: -element => 'hi'; or -element => ['hi1','hi2'] will both work.

    Custom tests will have the option of accepting arguments one at a time, or several at once, I plan to use prototyping for this.

    Comments, suggestions?


    My code doesn't have bugs, it just develops random features.

    Flame ~ Lead Programmer: GMS | GMS

[reply]
[d/l]
Re: Re: Re: Re: New Module Consideration?
by Anonymous Monk on Jan 26, 2003 at 03:07 UTC
    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.

[reply]

      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]
        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]
Re^4: New Module Consideration?
by Aristotle (Chancellor) on Jan 26, 2003 at 05:21 UTC
    I could still rank them 45 0 0 0 0 0 0 0 0. If this is permissible, why would it be unacceptable to make it 90 0 0 0 0 0 0 0 0? Of course, that just shows the example is bad and does not really discredit the idea.

    Makeshifts last the longest.

[reply]

In Section Meditations