> Fusebox's main weakness, IMO, is dangerous variable scoping
> across includes
> instead of CF custom tags. Custom tags give you nice encapsulated code
> objects with well-defined interfaces, but you can change variables
> willy-nilly in the stream of Fusebox CFINCLUDES and break code
> further down
> the chain. I don't like having so many global variables. For large-scale
> systems, it can be a nightmare to maintain and debug.
>
> We follow a Fusebox-like approach, but stress custom tags over
> includes. I
> don't know about the use of CFLOCATION in that example, it's not
> part of the
> Fusebox model.
>
> Fusebox must be considered an improvement, though, for sites with no
> standardized architecture at all.
I agree with this. You are exactly correct. This is the main weakness of
fusebox. Custom tags might give you performance hit, but the scoping issues
you mentioned are serious. I would like to hear any more you have to say on
how you structure you fusebox like apps with customtags.
-Bill
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
