How to convert legacy ColdFusion code to a framework?

Question

We have a medium-sized ColdFusion database for our Intranet and Website. For most of the history of the code, we used hard-coded links in cfm to where and where to “save” the code for tun.

In the past few years, we started using cfc to process more “navigation” code, as well as more automated save code (implicitly invoking the save process for a given cfc in init)

Assuming it makes sense to start using the framework, is it better to start using it for newer projects or to perform a full-blown conversion?

EDIT
To avoid confusion, I feel that by switching to a more cfc-based code, we are going down the path of randomly creating our own structure. It seems to me that taking a proactive step toward using the proper structure and allowing cfc to process the data is probably a wiser choice.

Answer 1

"Assuming it makes sense to start using the framework, is it better to start using it for new projects or try to perform a full-blown conversion?"

I would say that the biggest criterion for moving into the framework is:

• I spend a lot of time saving the current code, and is it difficult?
• ? ?

, , , , . , , , .

Answer 2

, 10-20% . ( .) , .

? , , .

Answer 3

.

, , .

Fusebox, , , .

, , - , - , cfswitch . dsp act qry fusebox .

- fusebox, . .

, , , .

ColdBox - , , , , ccc ... ..

Answer 4

, fusebox , ? , , .