Surely the program flow is more apparent in FuseBox because the entire flow
(and virtually nothing else) is defined in the FuseBox file. I like to be
able to read index.cfm, and see at a glance how the app flows.
Of course, you can make index.cfm pretty hard to understand by shuffling the
order of the FuseCations within your CFSWITCH, or you can choose an order
which has some relation to the way that users will move through the app.
Good names help too, of course. But I think that the FuseBox itself is the
greates aid to readability, comprehensibility that FB coding has going for
it.
Have fun,
Lee.
-----Original Message-----
From: Nat Papovich [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 3 May 2001 9:51
To: Fusebox
Subject: RE: RE: Managing program flow
Hopefully I don't sound like a person who hasn't done too much non-FB CF
worik, but why is the program flow more apparent in Fusebox? Is that because
you have named your fuseactions step1, step2, step3, etc?
Using a session variables are a really great way to do it, you could also
check cgi.query_string to make sure the user came from the previous
fuseaction step.
IMPORTANT NOTICE:
This e-mail and any attachment to it is intended only to be read or used by
the named addressee. It is confidential and may contain legally privileged
information. No confidentiality or privilege is waived or lost by any
mistaken transmission to you. If you receive this e-mail in error, please
immediately delete it from your system and notify the sender. You must not
disclose, copy or use any part of this e-mail if you are not the intended
recipient. The RTA is not responsible for any unauthorised alterations to
this e-mail or attachment to it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
