You know, people have been talking about the little
things they do and don't do since the beginning of
fusebox (that I remember) and still there's no
consensus. Especially for the benefit of the newbies,
I think we should all post circuit (or whole) apps
somewhere so we can really see what everybody's doing.
I'm making efforts toward this at
http://cfug.stampedenetwork.com
2cents
-ken
> > In a
> > more generic way we can say that each fuseaction
> would have some
> > initialization code and pointers to various
> subroutines. Personally,
> > I *never* let any business logic creep into my
> index.cfm.
>
> I try not to let logic into the various CFCASEs, but
> one of my objectives
> with Fusebox is the modularization and reuse of
> code. If an extra CFIF in
> index.cfm will let me repurpose a generic chunk of
> code, I'll add it.
>
> > Surely there are patterns that you use over and
> over?
>
> I don't personally consider the task of typing
> <CFSWITCH
> expression="#attributes.fuseaction#">once in each
> index.cfm all that
> onerous. [g]
>
>
> --
> Roger
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
