Hi Barry,

I haven't looked at fusebox in quite some time, and when I did look at it (several years ago), I had already tried developing applications in that model, and didn't like the results I was getting. Fusebox was a little more structured than my model, but, I didn't find my model all that helpful to begin with. Therefore, I found out even before I tried fusebox about the problems you've described, though I have a feeling it's not necessarily caused by fusebox, but just poor design (by the person who came before you), as you mentioned. Way back when CF had no such thing as CFC's, I found CF made it easier to do the wrong thing than the right thing, in general, as far as design is concerned. And, if I recall correctly, fusebox came about to help solve that problem - to make it easy to not only use MVC, but to almost force you into it. Of course, some of us are lazy and when we make a change, it is easier to put it in one place than try to sort out all the include mess and do the right thing. That sounds like what happened here, and if anything, I might say that is (again, from what I recall about it) the only way fusebox may have had a role to play in this.

In any case, I also would be interested to know what fusebox 5+ offers, so I think when I get some spare time I'll go have a look. I've been working in Java a lot the past couple of months, and I'm anxious to get back to CF development. As far as the one type of "app" you mentioned - I don't think that's what purpose it served, since CF has always made that easy via Application.cfm and Onrequestend.cfm. The changing guts then, would be all the rest of your files. If I recall, it was supposed to make MVC easier to follow.

-Sammy Larbi




Barry Beattie wrote:
hi all

please forgive this basic-level request for an overview about Fusebox,
but I'm just trying to get a better understanding on the big question
"why".

the last month or so has been my first real use of Fusebox. Sadly,
it's an FB3 app of a couple of years old  that I'm
extending/maintaining. In it there's bugger-all business processes
abstracted into functions (just heaps of qry_, act_ and dsp_ files)
and what CFC's that have been added are full of display code (HTML/JS
for pete's sake! - someone before me obviously got the wrong idea with
CFC's...). Also, cardinal sins of having too much logic embedded
within the fbx_switch files makes it a bit of a challenge to
appreciate what Fusebox does (and why).

I really miss having the controllers I'm used to and sometimes it
feels like FB is getting in the way or making things more complicated
than it needs to be. that and being annoyed by the lack of abstraction
like variables, queries, etc, created in one cfinclude but referred to
in another within the same switch. it just seems to make it harder to
get a good (quick) top-level grasp of each business process.

it may just be this old version or how it's used, but FB feels like
it's suited to easily build only one type of app  - common
head/footers, common nav, menues, etc, but with changing "guts".  The
use of Remoting, Ajax calls and self-posting forms are do-able but not
quite as straight-foward to what I'm used to.

is this a fair summary or have I got a dog of an example to be underwhelmed by?

Sure this is FB3 and FB5.1 is now out there, but as far as the core
features of cascading fbx_switch and fbx_settings files, what pain do
these actually solve?

any advice, opinons most welcome
thanx


You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm

CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com

An archive of the CFCDev list is available at www.mail-archive.com/[email protected]






You are subscribed to cfcdev. To unsubscribe, please follow the instructions at 
http://www.cfczone.org/listserv.cfm

CFCDev is supported by:
Katapult Media, Inc.
We are cool code geeks looking for fun projects to rock!
www.katapultmedia.com

An archive of the CFCDev list is available at 
www.mail-archive.com/[email protected]

Reply via email to