I actually do something similar, but I call a custom tag that I wrote that
loads different stylesheets (basename_browsertype)
depending on what browser is returned from CF_Browser.
This way, I can get something working in one browser, commonly IE and then
transfer all classes and tweak them according to the browser it would
display.
-----Original Message-----
From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 8:43 AM
To: Fusebox
Subject: Re: Hal's Dev Process & Stylesheets
> Couldn't a master stylesheet be somehow integrated with app_model?
> If you're putting stuff like:
> in app_model, it seems like a css stylesheet could be either cfincluded
from app_model, or some of it's
> functionality handled directly in app_model.
that's certainly what we do, but we just put a link reference as a value
like
<cfparam name="request.site.stylesheetlink"
default="http://www.georgebush.com/noapology.css">
and then actually load the stylesheet wherever we load the <head></head>
element (typically in the dspHeaderfile.cfm)
I actually like that a lot better than using request.page.fontcolor and the
like since stylesheets keep all that info together in one file
and one has a hard time arguing nowadays that "some browsers don't support
stylesheets"
(for a while we were including the stylesheet inline and then referring to
elements in it with the CF variables like
...myclass {color: #request.page.fontcolor#} ... boy, is that STUPID! :)
It's
too easy to break the style sheet and worse it has to get loaded for each
page rather than loaded as a link (so that it is cached for future pages).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
