Question

We have a medium sized ColdFusion code base for our Intranet and Website. For most of the history of the code we have used hard coded links in the cfm’s for where to go and for what ‘save’ code to tun.

In the last few years we’ve began using cfc’s to handle more of the “navigational” code as well as more automated save code (implicitly calling the save process for a given cfc on init)

Assuming that it makes sense to begin using a framework, is it better to begin using it for newer projects or attempt a full scale conversion?

EDIT


To avoid confusion, I’m sensing that by moving to more cfc based code we are going down the path of accidentally creating our own framework. It seems to me that taking a proactive step toward using a proper framework and allowing the cfc’s to process data is probably a wiser choice.

Answer 1

“Assuming that it makes sense to begin
using a framework, is it better to
begin using it for newer projects or
attempt a full scale conversion?”

I would say that the biggest criteria for whether you should move to a framework are:

1. Am I spending a good amount of time maintaining current code, and is it difficult?
2. Am I repeating a lot of code? Do you find yourself writing a lot of the same thing over and over when adding to the current project?

Depending on how large the application is, it might be worth it to convert a current application to a framework if it saves you more time down the road by making maintenance easier and reducing code repetition for future additions to the current project. If you rarely maintenance the application except for a few tweaks here and there, then I would say leave it alone and use a framework only for new applications.