Ok let me start by saying this. I have been writing CF for only a little over a year. In that time FB has been extremely helpful to me, learning programming concepts, organization, maintainability.
Let me also say this, I know who you are, and I know that you are eons above where I am in coding ability. However, if you are saying that FB is not a methodology then you are wrong. FLiP "tells you how to organize the development process". Now I don't think that XP needs to tell you how to organize your classes. That's inherent. With CF it's not. I still see sites all the time where you go from folder to folder, pointing directly at whatever.cfm and there is no organization. Just a quick step back from this. I think we are getting two separate parts of FB confused. Fusebox 3 is a framework. It is a way to organize and write your code to make it easier to maintain and follow. FLiP is a "methodology" that covers the development process. Now for a lot of the CF shops out there, methodology or process was non existent. You wrote a page with links going were they needed and then you wrote the page it linked to and so on. There was no real flow. Spaghetti code. FB 1-3 helped with this. It cleaned it up. It let people know where to look for something, and it made following the app a lot easier. Now for definition time: Mature: It has time. People have been using for several years, and it has grown. Open: Anyone can crack open the core files. make changes, suggest changes to the standard. standards based: following a standard. In this case there is a standards document that outlines what the core files should do, not how it should be implemented methodology: A body of practices, procedures, and rules used by those who work in a discipline or engage in an inquiry (taken from dictionary.com) Now I think FB is all of these things. I may be wrong. Tim Heald ACP/CCFD Application Development www.schoollink.net -----Original Message----- From: Dave Watts [mailto:[EMAIL PROTECTED]] Sent: Monday, April 29, 2002 11:02 PM To: CF-Talk Subject: RE: Fusebox (was: I like CFMX) > I am referring to FLiP. A process by which you can truly > get the most out of your requirements gathering, prototyping > and eventual coding. By using wireframe, mind maps and > prototypes with devnotes, to tear from the client what > they really need, not just what they think they need. These practices have existed long before ColdFusion was a glint in J.J. Allaire's eye. I hardly think you can credit them to Fusebox. This just illustrates the adage "what's old is new again" - many web developers ignored the lessons of the past and "discovered" all these things for themselves. If you're going to learn these things from Hal Helms, or not at all, by all means, learn all you can from Hal. Hal is certainly a smart guy. But don't make the mistake that there's something novel here. > Fusebox is a mature, open, standards based methodology. What does that mean? I don't even think it's a methodology at all, in the standard sense of the term. For example, eXtreme Programming is a methodology - it tells you how to organize the development process, but doesn't tell you how to organize your files. What standards does Fusebox use? What does it mean that it's open? Open to what? What makes it mature? Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
