Fusebox methodologies are analogous to an event handler in any sort of
Windows programming. The event model is not new to developers, and is a
tried and true practice. Moving that methodology to CF apps makes more
than enough sense to me. I use FB methodologies in my CF apps, and they're
easier to maintain not only by myself, but other developers here, beginners
to pros. They're easier to enhance, modify, and remove functionality. IMO
of course...
At 06:38 AM 12/20/00 -0800, you wrote:
>Some like it, some don't. I find it very
>helpful in an app I'm developing. For
>example, when I add a new functionality,
>the list of CFINCLUDed files is the same
>as similar functions, except for the one
>of two that are different. This is a
>WHOLE lot easier than cutting and pasting
>the right parts of a similar function
>coded in a single CFAS template.
>
>If you like it, use it, if you don't, don't.
>
>best, paul
>
>At 02:22 PM 12/20/00 +0000, you wrote:
> >Whats the whole point of Fusebox?
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
