Form Processing : the OO Way -- the Movie!
Yesterday, I posted a blog entry on doing form processing using OO to help us. There was a lot of code and some new concepts, so I thought having a couple of brief videos might be of help.
Do you like the idea of video (hopefully, I'll get better over time!) or do you find it annoying to watch a video about programming?
I think there is more value in a video. The only downside I see is that the audience is forced to go at the pace of the presenter. Some people, I'm sure would prefer to skip to just the transcript of the video.
Either way, you continue to provide great information! Thanks.
can understand the logic behind the code better as you explain it when you
walk through it. Thanks for the hard work.
2. In the second video, you mentioned how using a generic validator.cfc allows us to do server side validation such as "unique username". I'm trying to glue the concepts together in mind and I'm wondering what that rule would look like?
a. Would the validator.cfc have enough connections to other objects to perform the validation within validator.cfc? As in the actual "username unique" validation occurs in validator.cfc?
b. OR would the rule in validator.cfc simply be making a method call to another object that does the actual validation? In other words, the validator.cfc makes the call and returns the result but the actual work is done by the other object.
c. OR something else entirely.
Thank you.
Thanks for the kind words and encouragement. As for the low volume, I can amp that up.
@Gabriel,
I have a generic Validator.cfc that handles generic validation : isRequired, minLength, etc. But that Validator can be extended by other, custom validators that can handle things like "this user name has to be unique", etc.
@Akbar,
Certainly, I'll make the code available. Good idea!
@Henry,
No, that's just my CFElipse stuff.
I know it's just example code. But, I wanted to point out that in MyForm.pgm on line 12 the loop iterator variable should be 'var'ed (ie "for(var i=0"). Other wise i is in the window scope and can conflict with other loops.
Other than that, this seems like a very cool way of doing form validation.
Also, I bet you could make it so that if the user has JS turned off that you submit the form, use validator.cfc to give you a CF array and then render the validation messages back into the form...