We use a similar CFC-based system. It allows you to easily do things like switch layouts, or have several layouts per application. We use a xml file to define what directories receive a particular skin, and the call just remains #request.layout.header()#, etc on each page. Completely separates the presentation of headers and such from the content.
As for output from CFCs yes I'm against using output="true". There's no real reason the CFC itself should *force* output text onto a page. That said, the pattern of returning a string and then outputting the function call as a variable (like I showed above) is more flexible and (imo) not breaking OOP principles. Kam -----Original Message----- From: Will Tomlinson [mailto:[EMAIL PROTECTED] Sent: Sunday, February 12, 2006 4:15 PM To: CF-Talk Subject: Re: page layout: cfmodule vs customtags > I been using cfmodule for my page layouts but am making my current > project with customtags am curious what your opinions are on each and > why you'd pick one over the other. Layout.cfc - showHeader(), showLeftMenu(), showFooter() Works sweet! Screw custom tags! :) Will ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232115 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
