I have not worked with this specific method of validation, but
I have used this before and it works very well.
The js validation is going to be all client-side (as you probably know) so it’s somewhat independent of eForm. (At least that’s how I envision it)
In the past I typically create a new template for my form since I will call in some extra js files. I do this only so on 9 of 10 pages I’m not making extra server requests. (The 10th page being the form)
So, I would more than likely already be calling in jqery in a global js file. I will also need to call in the validation library.js file, and also my form-validation.js file. In that file I would set up my validation rules.
In the link I provided, my template would look like:
<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.4.4/jquery.js"></script>
<script src="assets/js/libs/jquery.validationEngine-en.js"></script>
<script src="assets/js/libs/jquery.validationEngine.js"></script>
<script src="assets/js/my-form-validation.js">
The top 3 calls are to the respective libraries.
The bottom call would be to a page that I build. It would look something like:
$(document).ready(function(){
// validation
$("#my-form-id").validationEngine();
});
// -- end DOM ready events -- //
My html of the form is pretty straight forward.
<label for="name">Name</label>
<input type="text" id="name" name="name" maxlength="40" value="" class="validate[required, custom[noSpecialCaractersSpaceOk]]" />
The "custom" is just a rule that I wrote to extend the existing "noSpecialCharacters" rule.
Since the js will stop any form processing before the server validates, you can also incorporate eForm’s validation. It should play nicely together.
Not sure I was much help but that is my experience.
☆ A M B ☆
☆ A M B ☆