Here is my two cents on the first question for what it is worth. If you are
going to use FB then you need to use FB everywhere. This would reduce the
training curve for anyone coming in after you. It isn't easy for someone to
learn that on this site we use this method and on this site we use FB. I'm
not saying that all sites have to be FB at once but a little at a time. Say
over a two to five year period for an example.
If the site is FB and the client wishes somewhere down the road to add
additional functionally to the site. You may wish at that point that the
site is FB. So why not do it from the get go?
Lee Foster
L3 Enterprise
-----Original Message-----
From: Patrick McElhaney [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 11, 2001 10:04 AM
To: Fusebox
Subject: RE: Handling Static and Dynamic Pages
First question:
I don't think FB makes sense at all for static sites
(or portions thereof). I only use FB for web based
applications.
Second question:
Use a pageID. Depending on what you mean by dynamic, though,
you may want to dynamically generate static pages. That is,
use cf to create html pages and save them with CFFile, and
update those files when something changes.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
