-Original Message-
From: Shannon Rhodes [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 20, 2003 9:54 AM
To: CF-Talk
Subject: Design Structure and cfinclude
The only part I'm still hesitant about is the navigation. I really do
wonder if I'm making it more complicated than it
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
One quick suggestion: put your CSS and javascript into separate .css and .js
files that get called into the header. That way the browser should cache. If
you just put code in the page header itself, yeah it has to download it
fresh each time.
I'm interested to see what other responses you get
September 2003 17:09
To: CF-Talk
Subject: Re: Design Structure and cfinclude
One quick suggestion: put your CSS and javascript into separate .css and
.js files that get called into the header. That way the browser should
cache. If you just put code in the page header itself, yeah it has to
download
Personally I dislike using includes this way for several reasons:
1) Eventually you will have a page that you DON'T want to have a
header/footer on and will have to add kludgy code to get around it.
2) Since the includes run in the same memory space as the main page you
have to worry about them
Shannon,
If you don't mind one level deep directories you can do a main
Application.cfm in the root - which defines the main variables you are going
to use (header file, css, meta tags etc.) and contains a cfapplication
tag. Then, instead of defining different groups of variables for each
One method we use is to create our pages as include files themselves. We
then build the main display page with simple code to set Page specific
information (like Title, template, etc.).
We have a template file for the application that includes the specified
files at the required point.
So I
:[EMAIL PROTECTED]
Sent: 19 September 2003 17:09
To: CF-Talk
Subject: Re: Design Structure and cfinclude
One quick suggestion: put your CSS and javascript into separate .css and
.js files that get called into the header. That way the browser should
cache. If you just put code in the page
FYI, another way to get Verity to read titles is by wrapping the title
tags
with CF comment tags:
!--- titleMy Title/title ---
I used to do that - but it doesn't seem to work any longer in MX (my
guess is that it was considered a bug and was picking up really
commented titles).
The
Shannon Rhodes wrote:
I think I need a balance between letting CF templates do it all for me,
and the tedious work of writing in each page information that is probably
the same 80% of the time in a given section.
Can anyone suggest a best practices approach to using cfinclude for
10 matches
Mail list logo
