Interesting to hear.
I will do a formal test on our network sometime when I get the chance and
report on my findings as well.
Out of curiosity, it wasn't an actual physical stop watch was it? Its far
less error prone to use something like the Net tab of Firebug or an external
plugin like Charles
re - Out of curiosity, it wasn't an actual physical stop watch was it?
of course not - it was an abacus! ;-)
nah in all seriousness, it was before the time of firebug, and around
the time of the birth of this mailing list.
yes it was literally a stopwatch - which was enough for me at the
time. i
There really needs to be a consistent method of sturucturing CSS personally.
If i cram everything onto one file I feel like the structure of the website
is not really effective and editing becomes a task. Most the time I will
break up the CSS file into a few sections as standard and use Yahoo!'s
James,
It depends on the site size and the structure. If you have a huge CSS
file for navigation
it is of course good to separate it from other styles.
I always make form.css for contact pages and form pages, but in general
i keep style.css
for the rest ad my sites are not so huge,
Lets have it. How are you guys structuring your CSS files?
I have been having a think about this over the last few days. My research
attempts have failed because most the articles i came across were outdated -
so i tend not to trust them.
One method i thought about (not sure if it's been coined)
re - How are you guys structuring your CSS files?
for me, multiple css files for different parts of the page is harder
to manage. I'm pretty old school keep everything within the 1 css
file (within reason). this also means 1 http request which is good.
exceptions are if you had a massive admin
Now that's a question to spark debate!
Without leaning one way or another there are a number of different
approaches you might try.
Have you considered CSS frameworks such as Blueprint CSS[1] or the 960
grid system[2]? These approaches help to standardize your CSS by
providing the basic page
How are you guys structuring your CSS files?
I am currently in the process of restructuring our CSS. The approach I'm
looking into is as follows:
1) use Eric Meyer's reset CSS to create a common base
2) use Blueprint's grid.css for the grid layer
3) use a component CSS layer to
a) give
page can turn a hobby into a million-dollar
business.” CNN Money
_
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Jens-Uwe Korff
Sent: Tuesday, 10 June 2008 12:04 PM
To: wsg@webstandardsgroup.org
Subject: RE: [WSG] Structuring CSS
How are you guys structuring your CSS
The way I structure my CSS is very much like you said - taking the Software
Development principles of Object-Oriented programming, and is pretty much
inline with what everyone else has said.
I generally break my CSS up to the following categories:
- reset.css : Reset all browser defaults.
Anton wrote...
-
In regards to I'm guessing this sort of structuring comes at a cost
because a number of requests need to be made to the server. this is
generally untrue. In principle this is exactly how download
accelerators work. They split a large file into smaller segments and
sent
11 matches
Mail list logo
