> 5. Lastly, OnRequestEnd.cfm has <cfinclude > template="includes/design/footer.cfm"> which tests for url.print and > delivers an appropriate footer based on this. The advantage is that I don't > have to include a footer on each individual page; the disadvantage is that I > can't use cflocation (since it doesn't call OnRequestEnd.cfm).
I highly recommend using a css print stylesheet. I've just started using them, and I find that they significantly reduce complexity for our sites. It moves the display code away from the application code which means less application testing. Once it's there you can forget it because it doesn't have anything to do with your application. In fact, we've added it retroactively to CF sites without altering any applicatoin code. And for us, where we have lots of completely static html pages, it incorporates those as well with no additional work. -Kevin ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm?link=i:4:137803 Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Get the mailserver that powers this list at http://www.coolfusion.com
