the idea of this technique is that each circuit is totally plug-n-play.
The circuit developer doesn't have any idea where the circuit would be
in the directory tree. So they wouldn't know what to set the
request.imagesroot to. Only the top-level architect that managed the
root index file would know where the directory is. The goal is that the
top-level architect doesn't need to manage each circuit application, he
only manages putting it all together.
It's neat idea and I think Fusebox should go in this direction, but i'm
not totally sold on it yet.
Steve
Shane Johnson wrote:
>
> Wouldn't it be cleaner to set each circuits request.imagesRoot in it's own
> "myLocals.cfm" ?
>
> -----Original Message-----
> From: Steve Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, December 14, 2000 10:38 AM
> To: Fusebox
> Subject: Re: the dot notation
>
> I have an idea....
>
> how about continue to use request.imagesroot or whatever. Have a
> default value in your application.cfm, then in your root index.cfm
> change the value in eash of the cfcases.
>
> cfswitch listfirst(attribs.fuseaction)
> cfcase value "cat"
> cfset request.imagesroot="/cat"
> cfset attribs.fa=listlast(attribs.fa)
> cfinclude cat/index.cfm
> /cfcase
>
> cfcase value "reg"
> cfset request.imagesroot="/reg"
> cfset attrbs.fa=listlast(attribs.fa)
> cfinclude reg/index.cfm
> /cfcase
>
> cfcase value "MainPage"
> cfset request.imagesroot="/images"
> cfinclude qry_GetStuff
> cfinclude dsp_DispMainPage
> /cfcase
>
> cfcase value "logout"
> cfset request.imagesroot="/images"
> cfinclude act_killsession
> cfinclude dsp_goodbye
> /cfcase
> /cfswitch
>
> Steve Nelson
> http://www.SecretAgents.com
> Tools for Fusebox Developers
> (804) 825-9063
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
