Chad,
One way to handle it is to save the content of one dsp_ file and
use it in another. It's kind of like using layouts, but not
actually using layouts.
<cfcase value="form">
<cfsavecontent variable="attributes.brokenOutPart">
<cfinclude template="dsp_brokenOutPart.cfm">
</cfsavecontent>
<cfinclude template="dsp_form.cfm">
</cfcase>
And sometimes the best solution is to just have two different
copies of the form, even if means some duplication.
Oh, and if you can make it to CFNorth... ;-)
Patrick
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 23, 2002 3:34 PM
> To: [EMAIL PROTECTED]
> Subject: breaking up dsp files
>
>
> Is it common to break up dsp files to increase reuse even if it means
> breaking up <form> tags?
>
> I have two forms that are very similar. I could have a bunch of CFIF's
> throughout the entire form that one files handles both forms
> but that seems
> overly messy. If I were to break out the differences into
> separate dsp files
> I could call them individually depending upon the fuseaction
> but that would
> mean either having a top dsp and a bottom dsp each with one
> half of the
> <form> tag OR spelling out the <form> tags in the fuseaction
> which doesn't
> seem to be proper form. Perhaps a third way would be to
> somehow use a layout
> to handle it but that doesn't seem practical.
>
>
> What is the best way to proceed?
>
>
>
>
> Chad Kemp
>
>
==^================================================================
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
==^================================================================
