views:

104

answers:

3

Hi I am new to OO frameworks in general such as MVC, Coldspring,etc but I have read about their benefits - could someone point tell me which one is the best - may be with standard to other programming language.

Many thanks

+2  A: 

"Best" is subjective. Each has strengths and weaknesses. We use Fusebox pretty extensively, and we have experimented with all the major ones. Fusebox matched the way we were already writing sites most closely, so we went with that.

MightyE
FuseBox is no longer under development.
Aaron Greenlee
@Aaron Greenlee: It isn't? Since when? I know that it has fallen out of favor in many places and I haven't heard much since Adam Haskell became the lead, but I didn't hear they'd stopped working on it.
Al Everett
Copyright troubles have stopped development. Here is a recent post by a FuseBox user pleading to resolve the issue: http://cfrant.blogspot.com/2009/08/open-letter-to-custodians-of-fusebox.html
Aaron Greenlee
+3  A: 

You can find a list of ColdFusion OOP frameworks on http://www.carehart.org/cf411/#cffw_app (includes links to their respective websites) So thats a lot. The most popular and most talked about frameworks nowadays are (IMHO):

  • FW/1 (became my favorite recently, modern, easy to learn, scalable. great performance)
  • Model Glue
  • ColdBox
  • CFWheels
  • Mach II
  • Fusebox

Which one is the best? You have to find out yourself, what fits your needs best.

Andreas Schuldhaus
+1 Bump for ColdBox
Aaron Greenlee
A: 

I have used both Fusebox and Coldspring. Which I would choose depends largely on the type of team and environments I was working with.

Fusebox is a classic MVC framework. The problem it is the best at solving is separating model and view. This is very handy when you have designers or dreamweaver jockeys who need to be kept out of the business logic and data access code. If you inherit a legacy ColdFusion project which was written as pages with includes for headers, footers, function libraries and the like, Fusebox may also be a good fit because it is very good at managing includes. In that case it may be fairly painless to take an unstructured site and bring it into a framework.

Coldspring is an entirely different beast and solves a different set of problems. It is (IMO) suited for more a "modern" development environment. It assumes you already have all of your business logic happily out of the designers way in CFCs and because of that now have the problem of managing the initialization and relationships among objects. To solve this it presents a "config file" of sorts for objects, all of their initial values, and their relationships to other objects. These are often called an object's "aspects" and this type of framework is often called AOP (aspect oriented).

Nick
thanks guys, I appreciate your comments