Someone in allaire's forums recently mentioned a problem that I am running
into now.
====
Calling a Fusebox application as a tag (i.e. calling the index.cfm file
through cfmodule/cfinclude) can have advantages and disadvantages.
The main advantage is that you can encapsulate complex file management and
processes through the very simple tag structure that is built into
ColdFusion. So instead of trying to figure out what files are needed to do
some action, you simple need to know the path of the index.cfm file (i.e.
template="/directory/index.cfm") the fuseaction you want to call (i.e.
fuseaction=somefuseaction) and any other variables that are needed for that
specific fuseaction.
The main disadvantage is when dealing displays. For example if you include a
layout display file that contains a menu within your application, then call
that application from some parent application that already contains that
menu layout you'll end up with two menus on the page. Which is most likely
not what you want.
* http://forums.allaire.com/devconf/Index.cfm?Message_ID=572223
====
Have any of you run into this, and how did you over come it?
I'm sitting at my desk right now, sipping a frosty cola beverage waiting for
someone to chime in. Please feel free to email me directly.
Thanks a ton.
-Russ
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
