No - not argumentative at all! I just didn't explain it terribly well. Here's my reasoning: the validation script contains X number of features and it's currently at version 2.5.1; it's a separate script that's independent of Form Tools, so I want it's numbering scheme to also be independent.
The only difference between the Form Tools bundled 2.5.1 version and the main 2.5.1 download file is that the initial configuration settings (which are all configurable) have been hardcoded to different default values at the top of the file. So it's the same script, same version: I just cut down on redundancy by specifying the same settings in one place, rather than multiple places.
I couldn't create a version 2.5.2, since the main RSV download file would always be 2.5.1 (the Form Tools-specific changes can't be included as default settings since they make no sense independent of Form Tools). Plus it wouldn't make sense to have a new release for a problem with the Form Tools-only version. Technically it wasn't even a problem: if you'd defined the g_rsvErrors function BEFORE including the script, it would have worked. But that's silly, so I figured it consistuted & bug and fixed it.
But ideally, the rsv.js script should remain untouched & I should have the custom settings defined elsewhere. I agree on that score. It was just more convenient this way.
That's pretty much it!
- Ben
The only difference between the Form Tools bundled 2.5.1 version and the main 2.5.1 download file is that the initial configuration settings (which are all configurable) have been hardcoded to different default values at the top of the file. So it's the same script, same version: I just cut down on redundancy by specifying the same settings in one place, rather than multiple places.
I couldn't create a version 2.5.2, since the main RSV download file would always be 2.5.1 (the Form Tools-specific changes can't be included as default settings since they make no sense independent of Form Tools). Plus it wouldn't make sense to have a new release for a problem with the Form Tools-only version. Technically it wasn't even a problem: if you'd defined the g_rsvErrors function BEFORE including the script, it would have worked. But that's silly, so I figured it consistuted & bug and fixed it.
But ideally, the rsv.js script should remain untouched & I should have the custom settings defined elsewhere. I agree on that score. It was just more convenient this way.
That's pretty much it!
- Ben