Is there a FluidAll.css?

[Jacob Farber]

Yes, this is critical too, thanks for pointing this out. I would think this would be ok as long as the content is collected in the order we suggest you output your <link> elements, if I understood you correctly.
Jacob

-----Original Message-----
From: fluid-work-bounces at fluidproject.org [mailto:fluid-work-bounces at fluidproject.org] On Behalf Of Aaron Brown
Sent: Wednesday, July 29, 2009 11:35 AM
To: fluid-work
Subject: Re: Is there a FluidAll.css?

Aaron Zeckoski wrote:
> I went ahead and wrote a shell command to build up the css files into
> a single one for now.
> find components/ -name *.css -exec echo "/*** file: {} */" \; -exec
> cat {} \; >> InfusionAll.css

That's a somewhat risky method for collecting the styles all together.
When the CSS files are read by the web browser, they'll be read in the
order they're declared in or referenced by the master style sheet.  This
is important since later declarations of entities with the same name
will override previous declarations.  Your shell script will work
provided there are no overlaps between common classes or ids and their
attributes.  If there is an overlap, you'll get a different result using
the script-generated style sheet.

If you want to write a script that produces an accurate
"InfusionAll.css", the script should follow rules similar to browser
processing and read/process all the nested @import statements to be sure
to concatenate the styles in the proper order.

 - Aaron

-- 
Aaron Brown :: aaron at thebrownproject.com :: www.thebrownproject.com

_______________________________________________________
fluid-work mailing list - fluid-work at fluidproject.org
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work