On the other hand if you had nothing but static *.htm files and had a couple
form submits you wouldn't need coldfusion much less fusebox.
Fred
----- Original Message -----
From: "McCollough, Alan" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Thursday, April 12, 2001 1:24 PM
Subject: RE: Handling Static and Dynamic Pages
> I'd fusebox everything. Fusebox serves as a means of linking pages
together,
> and it works great even if your content is purely static. If you had
nothing
> but .htm's for your display content, and had fuseactions hard-coded into
> your HREFs and form submits, you'd still get a lot of benefits.
>
> > -----Original Message-----
> > From: Tom Briscoe [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, April 12, 2001 9:12 AM
> > To: Fusebox
> > Subject: RE: Handling Static and Dynamic Pages
> >
> > Ok, we're getting a little closer to the core question here. Do you
stick
> > to Fusebox on "static" pages when it offers no other benefit but
> > consistency? Or Fusebox only your "application" elements of a site?
> >
> > I've done the latter in practice but I'm a single man development group.
> > : )
> >
> > As to generating static pages from dynamic elements, that sounds like a
> > good idea. I believe the Vignette StoryServer (a high priced content
> > management system if you're not familiar) uses that same method.
> >
> > Tom Briscoe
> > Web Developer
> > Compass Bank
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
