Fusebox fading out?

Forum|Forum|19 years ago
March 26, 2007
4 replies
634 views

Ok I see this post about coldfusion fading out, what about fusebox? We have started to try and use it in my organization (I'm the only web developer) and for whatever reason I HATE it. I feel like I'm in some kind of box, pun intended, and can't get out. My first major gripe was the inability to find a very good active forums like this one for fusebox specifically, the website its self sucks too, I had div's floating over to the center column and body text overflowing to the side, I mean cmon! So do you think that its being beat out by other frameworks, people dont use frameworks for coldfusion to begin with or what. I read stuff about frameworks being so great but especially in my position where I'm the only programmer I just can't see the benefit.

This topic has been closed for replies.

B

binxstaAuthor

Participating Frequently

Yea I guess your right, I suppose I'll have to get used to it, I had just gotten comfortable with my own little mini framework and I dont like people telling how to do things, hah.

S

SafariTECH

Inspiring

Well, I don't use "Fusebox" the application, but I pretty much develop all my applications using the fuseboxing technique.

I am on my own now, but when I was IT head and main programmer for a CF House here, we all used the fusebox technique for creating sites. The architecture surrounding that was up to each individual developer.

As long as the programming is properly commented, then any other developer could pick it up and continue the project. Without comments, pretty much any technique ( aside single page programming) is very tough to figure out w/o the original programmer.

Based on some of the questions and responses on these forums alone, I would have to guess that well over 50% use a "fuseboxing technique" for application development. They just may not use the actual Fusebox application.

Sometimes you just have to analyze the pros and cons on a per project basis. There are places where you may find it doesn't work easily.

B

binxstaAuthor

Participating Frequently

>Well, I don't use "Fusebox" the application, but I pretty much develop all my applications using the fuseboxing technique.

So your saying you dont use the actual circuits and xml grammar that fusebox parses into code? Does that mean you basically just organize things so that the index page calls everything? I've talked to a lot of people and never heard someone that mimics fusebox but doesn't actually use the framework files that have been developed.

>If I would have to wildly guess at a number I would say 3-5% use a framework
>alone, I would have to guess that well over 50% use a "fuseboxing techniq

Wow those are some wildly different guesses

T

TSB

Inspiring

I mimic fusebox but don't use the fusebox files. I use index files to control everything. Most of my apps are small projects. The only special file I need is the cf_formURL2Attributes custom tag.

Trevor

B

binxstaAuthor

Participating Frequently

Well to break it down to a simpler question. Out of all the CF devs out there how many use a framework and out of them how many use fusebox. (Feel free to make outrageous guesses).

J

JohnEric

Inspiring

If I would have to wildly guess at a number I would say 3-5% use a framework such as Fusebox, Mach-II, or Model-Glue. If you have anything approaching a larger site there is probably something to help organize it, even if it is a homegrown framework.

I primarily use Model-Glue and Mach-II so can't really talk about using Fusebox but, in general a framework allows you to separate concerns, encapsulate functionality, and organize developement.

Separation of concerns is important from a maintenance standpoint. You're not supposed to mix application logic and display logic. The more complex a site gets the harder it is to understand what any specific page is supposed to be doing. When you come back to change something you wrote six months ago, it can be a real challenge to understand what you did and to be able to change the functionality.

Encapsulation of functionality is important for both maintenance and code reuse. When a bug is found you only have to fix it in one place rather than ten. When you need to use the same exact functionality in several places you only need to call one thing.

Organization of your developement really helps when you have more developers working on a site but, even with one you have the benefit of knowing where any bit of code should go. The frameworks help by giving you a sort of classification system for pieces of code that you have rather than having them floating around randomly in your directory structure.

S

SafariTECH

Inspiring

Fusebox is actually a development technique and not really specific to CF.

While I know somebody came up with the idea of creating a product called specifically "fusebox", it was derived on the technique.

Fuseboxing is just the technique of using 1 file to call and include other files into teh page to generate the required output ( like placing fuses in a fusebox ... I know, nobody uses fuses anymore either, they have breakers now, but same thing). This gives you smaller individual files to work with and debug if there is a problem.

You can apply "fuseboxing" to pretty much any development platform all on your own.

BTW, CF is not fading out ... Enterprise level businesses and organizations still use it quite a bit and there are no lack of jobs for CF devs on sites like Monster. The choices for Enterprise level app servers is really limited to only 3 products, of which CF is in the middle.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded