Comments on: JS based easy Field Validations in Rails http://www.anup.info/2008/01/06/js-based-easy-field-validations-in-rails/ Freelance RubyOnRails Developer, London Fri, 05 Dec 2008 09:16:14 +0000 http://wordpress.org/?v=2.6.2 By: Tarun Chandel http://www.anup.info/2008/01/06/js-based-easy-field-validations-in-rails/#comment-12522 Tarun Chandel Mon, 28 Jan 2008 10:18:27 +0000 http://www.anup.info/2008/01/06/js-based-easy-field-validations-in-rails/#comment-12522 Hi Anup I like you blog, especially because I am trying to learn RoR and I was just collecting some resources for getting started. Your blog will surely be of help, keep up the good work :) Tarun Hi Anup

I like you blog, especially because I am trying to learn RoR and I was just collecting some resources for getting started. Your blog will surely be of help, keep up the good work :)

Tarun

]]> By: Jim Cropcho http://www.anup.info/2008/01/06/js-based-easy-field-validations-in-rails/#comment-10677 Jim Cropcho Sun, 06 Jan 2008 20:13:08 +0000 http://www.anup.info/2008/01/06/js-based-easy-field-validations-in-rails/#comment-10677 "Most of you will disagree with this post to use Javascript based form validations in Rails." I don't, depending what your needs are. Client-side form validation can greatly reduce the amount of POSTs you app has to handle (and reduce your bandwidth costs, by extension). At the same time, the current design methodology of such systems makes validation logic a lot less DRY, because ORM-layer validations are specified in model classes, and client-layer validations are specified in view documents (i.e. rHTML files)- a separate problem in itself. A DRY, elegantly-designed client-side validation system would store validation logic which is shared between both layers in a single location, while also allowing rules which only apply to one layer to be specified, as well. “Most of you will disagree with this post to use Javascript based form validations in Rails.”

I don’t, depending what your needs are. Client-side form validation can greatly reduce the amount of POSTs you app has to handle (and reduce your bandwidth costs, by extension).

At the same time, the current design methodology of such systems makes validation logic a lot less DRY, because ORM-layer validations are specified in model classes, and client-layer validations are specified in view documents (i.e. rHTML files)- a separate problem in itself.

A DRY, elegantly-designed client-side validation system would store validation logic which is shared between both layers in a single location, while also allowing rules which only apply to one layer to be specified, as well.

]]>