Personally, I wouldn't put any display elements in application.cfc but rather use it for app setup purposes (defining global variables, initialising shopping carts, etc). If you wanted to have a different page template on a page it might be a big hassle -- or one day you may want a page that delivers RSS or CSV or something else. Depending on the way your site is structured, you may find custom tag pairs are a nice way of wrapping templates around your pages....
<template:normal title="my page"> ... ... ... </template:normal> -----Original Message----- From: Will Tomlinson [mailto:[EMAIL PROTECTED] Sent: Wednesday, 9 November 2005 2:46 p.m. To: CF-Talk Subject: cfinclude from a template, or onRequestStart? I usually assemble my pages with a cfinclude header, menu, footer, etc. But I figured it might be better to include the header.cfm in onRequestStart, and footer.cfm in onRequestEnd to keep from spreading includes all over the place. This way they'd all be in one spot. Am I thinking right?? Thanks, Will ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:223633 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
