Comments on: Playing with JQuery Validation Library, Part 2 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/ Fri, 12 Mar 2010 14:11:39 -0600 http://wordpress.org/?v=2.8.6 hourly 1 By: Drito http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/comment-page-1/#comment-50501 Drito Fri, 20 Nov 2009 14:31:27 +0000 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/#comment-50501 If you want to include data that will be evaluated at the time of the validation and not only once when the page is loaded, it seems that you can even include fields in the form of functions : remote : { url: 'ManageClients.do', data: { action: 'validateUniqueField', id: function(){return $('#clientFormDialogId').val();} } } Like that, the $('#clientFormDialogId').val() will be run each time the validation is executed. In my case it was necessary because the form is inside a Dialog widget and it is populated via AJAX, so the same form can be used for several objects, and the id element will have no value at all when the page is first loaded, and its value dynamically changes every time an object id loaded into the form. If you want to include data that will be evaluated at the time of the validation and not only once when the page is loaded, it seems that you can even include fields in the form of functions :

remote : {
url: ‘ManageClients.do’,
data: {
action: ‘validateUniqueField’,
id: function(){return $(’#clientFormDialogId’).val();}
}
}

Like that, the $(’#clientFormDialogId’).val() will be run each time the validation is executed.

In my case it was necessary because the form is inside a Dialog widget and it is populated via AJAX, so the same form can be used for several objects, and the id element will have no value at all when the page is first loaded, and its value dynamically changes every time an object id loaded into the form.

]]> By: Sergio Pereira http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/comment-page-1/#comment-50056 Sergio Pereira Sat, 31 Oct 2009 19:46:19 +0000 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/#comment-50056 If you want to pass more data to the "remote" rule, you can customize the call a lot by passing an options object instead of just the url, like: remote: { url: '', type: 'post', data: { user: $("#userNameEdit").val(), otherParam: 123 } } If you want to pass more data to the “remote” rule, you can customize the call a lot by passing an options object instead of just the url, like:
remote: {
url: ”,
type: ‘post’,
data: {
user: $(”#userNameEdit”).val(),
otherParam: 123
}
}

]]> By: James http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/comment-page-1/#comment-49962 James Tue, 27 Oct 2009 14:37:21 +0000 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/#comment-49962 Hello Chris, When you get a chance, check out MVC2 Preview 2. This framework solves the client/server-side validation dilema. This is easily implemented in three steps. First, add attributes or DataAnnotations, to your domain model. Then add these three scripts already included in your MVC project: jquery-1.3.2.js, jquery.validate.js, and MicrosoftMvcJqueryValidation.js. Finally add this line of code to your View: There are several advantages here. Client-side validation is the default and if the user has javascript disabled server-side validation is conducted. All of your validation rules are in one location so it is easy to maintain, and you have accounted for both client and server-side validation. What I do not like is it takes the fun out of writing your own jQuery :( For an easy example read this: http://blogs.msdn.com/rickandy/archive/2009/10/03/client-side-validation-for-mvc-2-p2.aspx Thanks for your post, James Hello Chris,

When you get a chance, check out MVC2 Preview 2. This framework solves the client/server-side validation dilema.

This is easily implemented in three steps. First, add attributes or DataAnnotations, to your domain model. Then add these three scripts already included in your MVC project: jquery-1.3.2.js, jquery.validate.js, and MicrosoftMvcJqueryValidation.js. Finally add this line of code to your View:

There are several advantages here. Client-side validation is the default and if the user has javascript disabled server-side validation is conducted. All of your validation rules are in one location so it is easy to maintain, and you have accounted for both client and server-side validation. What I do not like is it takes the fun out of writing your own jQuery :(

For an easy example read this:
http://blogs.msdn.com/rickandy/archive/2009/10/03/client-side-validation-for-mvc-2-p2.aspx

Thanks for your post,
James

]]> By: Reflective Perspective - Chris Alcock » The Morning Brew #463 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/comment-page-1/#comment-49957 Reflective Perspective - Chris Alcock » The Morning Brew #463 Tue, 27 Oct 2009 07:36:05 +0000 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/#comment-49957 [...] Playing with JQuery Validation Library, Part 2 - Chris Brandsma resumes his series looking at JavaScript validation using the JQuery Validation Library, and in this part tackles validation using AJAX validators to check back with the server to see if a value is valid [...] [...] Playing with JQuery Validation Library, Part 2 – Chris Brandsma resumes his series looking at JavaScript validation using the JQuery Validation Library, and in this part tackles validation using AJAX validators to check back with the server to see if a value is valid [...]

]]> By: BjartN http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/comment-page-1/#comment-49956 BjartN Tue, 27 Oct 2009 06:27:09 +0000 http://elegantcode.com/2009/10/26/playing-with-jquery-validation-library-part-2/#comment-49956 Small tip on making javascript maintainable: Put it in a separate file and don't inline server code :) Of course it works for a demo :) Small tip on making javascript maintainable: Put it in a separate file and don’t inline server code :) Of course it works for a demo :)

]]>