> > Why not? (asked looking for a legitimate reason, IE: x or y won't work > properly if you do)
There's no solid reason *not* to, that I'm aware of, other than design choice. I have built a display framework like this in the past and after it launched I found that there was no real reason *to* put this kind of display logic in a cfc because regular templates and custom tags handle this perfectly (and were designed for this purpose). The design choice is in separating logic from display; components for logic, custom tags and coldfusion templates for display; clean. Having said that, having an object that is an 'html framework' doesn't present a particular problem if it is separated from business logic. Perhaps someone can chime in with solid disadvantages to the display cfc approach - for me, it is as simple as a) going with consensus b) making separation of logic and display very clear. I realised that changing framework isn't realistic halfway through (or more) a project and I'm *not* saying *DONT* do what you are doing" Just raising it as something to check out, if you weren't already aware, as you said you were starting to write apps using cfcs. I personally found using an MVC framework answered all the questions I had about creating apps utilizing cfcs. HTH Dominic -- Blog it up: http://fusion.dominicwatson.co.uk ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:304620 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
