![]() Then I discovered that jQuery, the most popular JavaScript library in use today, could do a lot of the validation I needed as well as anything else. ![]() The first standard I adopted was “ValidateThis”, a full featured form validation framework for ColdFusion. I started looking for some standards and I found two I really liked. But that too caused issues, because no two people will write form validation the same way. Many times I ended up writing my own JavaScript form validation, because it was slimmer and markedly faster. With CFFORM we were promised rich looking forms that could present themselves in HTML, Flash, or XML. The CFFORM tag was supposed to bring a certain aesthetic to an otherwise drab developers skill set. It may sound like heresy for a ColdFusion developer to openly say he doesn’t use ColdFusion for everything, but there are certain tasks where other toolsets are often better and/or faster to use. For the purposes of this post, I will be talking about the language side of ColdFusion and when I prefer not to use it. To be clear, ColdFusion is both a server platform and a scripting language. However, ColdFusion does not solve every problem. I have seen many improvements in the language over the years. It is my primary development language and it has kept me gainfully employed for about 14 years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |