Sent by markinoregon on 23 July 2003 19:07
I allways structure mine according to the FLOW of the page,
for example for a 3 column CSS layout:
body {
blah blah
}
right-content {
blah-blah
}
center-content {
blah-blah
}
left-content {
blah-blah
}
footer {
blah-blah
}
then style the p, h1,'s a's,,,,etc
markinoregon
Website under construction (as allways)
www.markthesteelhead.com
-----Original Message-----
From: [EMAIL-REMOVED]
[EMAIL-REMOVED]]On Behalf Of Alex Jones
Sent: Wednesday, July 23, 2003 9:23 AM
To: Alicia Lane; [EMAIL-REMOVED]
Cc: Alex Jones
Subject: Re: [css-d] CSS Methodologies
At 10:40 AM 7/23/2003, Alicia Lane wrote:
>I agree - I list all general attributes first and then tackle the document
>structure and specific attributes, in order of location.
>
>This method also makes it easier to troubleshoot bugs. With the style rules
>ordered by location, you can examine a troublesome spot AND the rules being
>applied to elements surrounding it. An alphabetical listing of style rules
>would make this very difficult.
Hrrrm, the way I tend to name my classes and IDs ensure they are grouped,
even within an alphabetized framework. But unless I am wrong about the
cascading order (more info in a previous reply to Nelson Rodriguez-Pena) I
do not see how this is very beneficial. If you change the structure of the
(X)HTML at a later date you would have to return and restructure your CSS -
even if the styles didn't change. Also, how would you address a class or ID
that might be placed in a different part of the structure depending on the
page or module being viewed? Does that make it a general attribute?
I do see value in grouping the general attributes and then structure, but
I'm trying to question everything (including my own assumptions). :)
Playing the devil's advocate.
>Besides, applications usually have shortcut keys for the "Find" function if
>you're looking for a specific rule, so that seems to eliminate the need for
>alphabetical indexing.
Well, different people use apps in different ways. :) While I like to use
the find function often, some designers and developers either don't think
to use it, or are just wired to scroll.
>Great idea to put together a methodology. I'd love to see the finished
list.
This is a great discussion so far, please keep it up! If people are
interested, I would be more than happy to set up a site to start gathering
and archiving the discussion to turn into some documentation. It would be
easy enough to set up multiple authors for those interested in actively
participating.
Alex
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
