There is also QForms if you want to google that.  It was implemented pretty 
well.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED]
Sent: Monday, February 26, 2007 7:25 AM
To: [email protected]
Subject: Re: [ACFUG Discuss] validation techniques for existing application



There is a reusable-extensible (server side) validation component in my Tardis 
framework.  Feel free to check it out and if you like it, just grab it out of 
the framework and do whatever you please with it. If you have any questions 
about it, feel free to contact me off list. 

http://www.illumineti.com/blog/index.cfm?mode=cat&catid=28B26753-C09F-25C5-832AE045709158C1
 


Shawn Gorrell
Web Development Applications Architect
Federal Reserve Bank - Atlanta
Office (404)  498-8449 



"Ajas Mohammed" <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED] 


02/25/2007 12:52 AM 


Please respond to
[email protected]



To
[email protected] 

cc

Subject
[ACFUG Discuss] validation techniques for existing application

        




Hi,
   We have about 5 web applications which fork from the same code, but ofcourse 
they have own customizations and also differ a lot from each other as the 
clients are different, meaning different needs and lots of different code even 
though the origin is the same code. 
Whenever we have new client, we use the code and the code grows from there on.

Now to my main question. We dont have proper validation in any of our 5 or 
whatever no. of code we have. The main code which we use is so mixed with 
different validation that I cannot explain i.e. some cfforms, some javascript 
validation, some hidden fields i.e _required validation etc. So I was thinking 
that next time we have a new client, I should (or my team) add validation to 
the code we use such that we have all things covered atleast User interface * 
error description etc those kind of things. I wanted to know how to handle 
this? can anyone share there experience. What I wanted to achieve was a code 
reusable approach so that if I need same validation elsewhere I dont have to 
write it again. Something on the lines of CFC's I would say. 

This is my own interest and I will do at my own time. No one is bothered or 
care to have this functionality. Its just that the developer inside me cannot 
live with this fact that the application is not Perfect. I want it to be 
Perfect. After all, you live and die by your code. 

-- 
<Ajas Mohammed />
 <http://ajashadi.blogspot.com/> http://ajashadi.blogspot.com 
------------------------------------------------------------- 
To unsubscribe from this list, manage your profile @ 
 <http://www.acfug.org?fa=login.edituserform> 
http://www.acfug.org?fa=login.edituserform 

For more info, see  <http://www.acfug.org/mailinglists> 
http://www.acfug.org/mailinglists 
Archive @  <http://www.mail-archive.com/discussion%40acfug.org/> 
http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by  <http://www.fusionlink.com/> FusionLink 
------------------------------------------------------------- 

------------------------------------------------------------- 
To unsubscribe from this list, manage your profile @ 
http://www.acfug.org?fa=login.edituserform 

For more info, see http://www.acfug.org/mailinglists 
Archive @ http://www.mail-archive.com/discussion%40acfug.org/ 
List hosted by FusionLink <http://www.fusionlink.com>  
------------------------------------------------------------- 




-------------------------------------------------------------

To unsubscribe from this list, manage your profile @ 

http://www.acfug.org?fa=login.edituserform



For more info, see http://www.acfug.org/mailinglists

Archive @ http://www.mail-archive.com/discussion%40acfug.org/

List hosted by http://www.fusionlink.com

-------------------------------------------------------------


Reply via email to