Yeah, I actually use variables.section.stylesheet as
well as variables.page.stylesheet so that you can
include a section/site specific stylesheet and a page
specific stylesheet as well.
However, my question was more geared to the
architecting/prototyping/development process. I am
trying to find the best way to keep development and
layout separate and was wondering how all of you do
it.
How do you keep your developers from having to have a
knowledge of the app's styles and layout? Obviously,
it saves time and energy if those things are already
set before they get to the developer, so that he/she
does not have to fish around in a stylesheet and try
to figure out what color to make h2 tags in his/her
code or which class to use on his/her p tags.
Hal's process seems pretty solid, having 'prototyped'
pages already available for the developer so that the
layout is set and he/she just puts in the CF code
around it.
Anyone else have any thoughts or ideas?
Nate
--- Ken Beard <[EMAIL PROTECTED]> wrote:
> how about request.page.stylesheet
> or we could reinvent the wheel :)
>
>
> At 09:59 AM 4/12/01 -0500, you wrote:
> >Hey, Nate.
> >
> >Couldn't a master stylesheet be somehow integrated
> with app_model?
> >If you're putting stuff like:
> >
> >cfparam name="request.page.bgcolor"
> default="800000"
> >cfparam name="request.page.font.color"
> default="FFFFFF"
> >cfparam name="request.page.link.color"
> default="FFCC66"
> >
> >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.
> >
> >Yes? No?
> >
> >
> >Steve
> >
> >
> >Nathan Shaw wrote:
> >
> > > This question is mainly directed at Hal, but I
> would
> > > love to hear how the rest of you deal with this
> as
> > > well.
> > >
> > > When you are spec'ing out an app, where/when
> does the
> > > layout and master stylesheet come into play?
> > >
> > > >From what I know of Hal's method, it seems as
> if the
> > > design and the master style sheet would be made
> before
> > > the fusedocs headed over to the Phillipines. So,
> do
> > > you, Hal, tell your developers which classes to
> use in
> > > their dis_ fuses? (Like, use a H2 tag for all of
> your
> > > headers and a .subhead class for all subheaders)
> OR,
> > > do you let them do plain vanilla development of
> the
> > > fuse and then have a producer/layout person go
> in
> > > afterwards and apply formatting? OR is it
> something
> > > else entirely?
> > >
> > > It seems to me that the CSS master sheet should
> be
> > > part of the main spec'ing & design process so
> that you
> > > could hand a developer a fusedoc and a master
> style
> > > sheet so that they could apply styles as well as
> they
> > > coded the fuse. This would prevent the need for
> a
> > > producer to go in afterwards and pretty up the
> site.
> > >
> > > How do you all deal with this?
> > >
> > > Nate
> > >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
