allthough most here would aregue that your business logic should at least be in a separate CFC so that the code is re-usable. There are some good form handlers out there that do all the validation and generate nice error messages for you. here is one off the top of my head http://pengoworks.com/index.cfm?action=get:qforms
On Mon, Apr 30, 2012 at 6:32 PM, Christopher Watson <[email protected]>wrote: > > > As long as you have some separation.. > > [code examples snipped] > > One of the strengths of ColdFusion (and, indeed, other languages of its > ilk) is that you don't have to separate your input interfaces from your > back-end processing, and even the response display. There are sound reasons > for implementing direct feedback form input interfaces within a single > template, conditionalizing the function points. In some cases, good UI and > app design dictate that it all be rolled into one, because the input, > processing, and response may all be visually integrated (i.e., what you > enter into the form and submit comes back at you in a processed form, > providing necessary results feedback). If your input UI is the basis for a > self-same response display, then it makes perfect sense to roll it all into > one template, allowing one to maintain that code in a single place. But of > course, YMMV. I just wanted to make note that there's nothing inherently > bad about designing things that way. > > -Christopher > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:350901 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
