Cfinput not validating
It was easy to use (well, maybe not in DBML, but we fixed that quickly, and using it got even easier and simpler in subsequent versions), and it just worked.
To this day, the brilliant simplicity and power of which made programmatic delivery of SMTP email messages as simple as it could possibly be.
And now, what is right is to use Cold Fusion for back-end functionality, and to stop using Cold Fusion client-side abstraction features. I am indeed using Cold Fusion for what it does best, for what it does better than any of the alternatives, but I have stopped using it where other technologies are preferable.
I hope this explains my statement, and I'd love to hear your thoughts on the subject.
And so, like many other Cold Fusion developers, I used ).
Then a single line of code turns the table into a paginated grid that is sortable, searchable, and completely customizable.
And then we added the ability to work with spreadsheets, and manipulate images, and communicate with Exchange servers, and so much more, all in the name of greater productivity.So I am using j Query validation libraries instead of tags? These all need to be supported by Cold Fusion to maintain backwards compatibility, but there just is no good reason to keep advancing them, and even less reason for you to use them in new development.Cold Fusion client code generation features just don't make that much sense anymore.Rather, they were the ones that used the best technology for the job, all held together by Cold Fusion glue.That's why Cold Fusion supports XML and Web Services and server-side Java and CFXs and even . The objective has always been to use the right tools for the job, recognizing that what is right for one project may not be right for another, and that what is right today may not be right tomorrow.As you may have noticed, my website recently underwent a significant facelift as explained in a blog post made a couple of days ago.