.
From: Matthew Walker [EMAIL PROTECTED]
Sent: Tuesday, November 08, 2005 9:12 PM
To: CF-Talk cf-talk@houseoffusion.com
Subject: RE: cfinclude from a template, or onRequestStart?
Personally, I wouldn't put any display elements in application.cfc but
rather use it for app setup purposes
.
-Original Message-
From: dave [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 9 November 2005 11:47 p.m.
To: CF-Talk
Subject: RE: cfinclude from a template, or onRequestStart?
He's not saying to but the actual html in the app.cfc file he's saying
put the include. And I don't see why you couldn't
Subject: RE: cfinclude from a template, or onRequestStart?
I don't see why you couldn't or wouldn't
Well you certainly could, although I wouldn't. It is the kind of thing
that may not be a problem now but could be a hassle later. As you
describe in your first paragraph below, it's a hassle when
Depends on who you ask. That is an easy way to handle headers and footers in a
simple site, but it violates MVC principles, so if you are looking for a
cleanly separated View, you shouldn't go that route.
I generally don't bother with MVC for quick and dirty apps or mini-sites, but I
use a
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
Good points guys! 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
On 11/8/05, Will Tomlinson [EMAIL PROTECTED] wrote:
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
7 matches
Mail list logo
