I guess part of our problem is we've always done it "backwards". Ie - we've got code that will take a database schema and create a fully functional form and all necessary files to make it work in Fusebox. It's then relatively easy to apply html to "pretty it up". The reverse (starting with an html form and applying cf), is way more time consuming.
Don't get me wrong, I *believe*... I'm just looking for the best way to retain the benefits of our backwards approach but also keep beni's of prototyping.... Has anyone else found a way to strike this balance (or do you just suck up the cost of the html - knowing you get it back in the long run)? -- Michael Rahmn -----Original Message----- From: Jeff Peters [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 12:51 PM To: [EMAIL PROTECTED] Subject: RE: FLiP and Prototyping Typically, you're not coding *again* in Fusebox. Rather, you're taking the existing HTML form and inserting whatever CF you need to make it dynamic. ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
