> I understand the "black box" principle of CFC's, make sure that your cfc's > can stand on their own as black boxes. When doing OOP based development, > does this paradigm extend to non-cfc ColdFusion files, IE: display and action > pages.
In general, any program should have a defined set of inputs and outputs, and CFML pages are no different. However, dependencies are much more acceptable in CFML pages than in CFCs. For example, includes, references to external scopes, etc - that's all fine in CFML pages. So, my overall advice here would be not to overthink display logic - it's the least "formal" layer in an HTML-based MVC application. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335983 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
