> > Fusebox just tells you how to organize your code > > Me thinks it's time you learn more about Fusebox if simple > code organization is what you think it's all about. That's > an old wives tale that seems to live on...and on...and on...
It may be a slight oversimplification, but it's a useful one. So, you've got the ability to build "circuits", and relationships between those circuits. To me, largely, that boils down to how you organize your code within files. Now, there's nothing wrong with that - it doesn't hurt anything, in the grand scheme of things. My problem with it is as it's always been - it doesn't address the big issues. How do you partition your application logic? What logic are you moving to the database? (Or, with CF MX, what logic are you going to move to a middle tier?) What logic are you moving to the client? How are you minimizing the amount of work done at runtime? Frankly, if your biggest problem is "how do I make this piece of CF code interact with that piece", take the rest of the day off. As for learning more about Fusebox, I've never been able to find a definitive, single source for documentation. Why is that? I mean, there's a sample app, there's a bunch of bits and pieces of help docs, but there's no standard - no RFC or the like - no one single authoritative document like there is with any similar initiative. It seems to be a bit vague in that respect. Contrast that with the RFC for HTML, or any other standard, which while it may be stultifyingly boring, is both adequate and complete. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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
