On 1/09/2011 7:31 PM, Tim Dawson wrote:
On 31/08/2011 17:34, Kevin A. Cameron wrote:
The talk was interesting, but the camera work poor. Too much
presenter, it was difficult to see the slides.
Did anyone catch what she talking about towards the end; it sounded
like 'pre-' something.
Tim
On
On 31/08/2011 17:34, Kevin A. Cameron wrote:
My favourite part from that presentation was when she said
(paraphrased) what's between the brackets is trivial, it's the
selectors that are the tricky part.
Kevin
The talk was interesting, but the camera work poor. Too much
presenter, it was diffic
-boun...@lists.css-discuss.org] On Behalf Of Tim Dawson
Sent: Wednesday, August 31, 2011 10:54 AM
To: css-d@lists.css-discuss.org
Subject: Re: [css-d] CSS Organization
On 31/08/2011 17:34, Kevin A. Cameron wrote:
> My favourite part from that presentation was when she said
> (paraphrased) wha
I'm guessing that was preprocessors, the likes of LESS or SASS.
Kevin
On Wed, Aug 31, 2011 at 10:53 AM, Tim Dawson wrote:
> On 31/08/2011 17:34, Kevin A. Cameron wrote:
>
>> My favourite part from that presentation was when she said (paraphrased)
>> what's between the brackets is trivial, it's
On 31/08/2011 17:34, Kevin A. Cameron wrote:
My favourite part from that presentation was when she said (paraphrased)
what's between the brackets is trivial, it's the selectors that are the
tricky part.
Kevin
The talk was interesting, but the camera work poor. Too much presenter,
it was diffi
My favourite part from that presentation was when she said (paraphrased)
what's between the brackets is trivial, it's the selectors that are the
tricky part.
Kevin
__
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discus
On Aug 31, 2011, at 2:38 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
>> Let's suppose that by looking to those wireframes, I can say that all my h2
>> will have a padding-bottom of 10px.
>> However, if later on, I create a rule telling that the ul will have a margin
>> top of 5px... (because al
On 30-08-2011 19:31, Ingo wrote:
mem schrieb am 30.08.2011 19:31
I must develop the CSS for those 100 pages and I'm really afraid about
the fact that, I will have, almost surely, rules that will overwrite
each other and it will be a mess, sooner or later.
Here is an interesting discussion:
h
mem schrieb am 30.08.2011 19:31
I must develop the CSS for those 100 pages and I'm really afraid about
the fact that, I will have, almost surely, rules that will overwrite
each other and it will be a mess, sooner or later.
Here is an interesting discussion:
http://www.stubbornella.org/content
mem wrote:
> Let's suppose that by looking to those wireframes, I can say that all my h2
> will have a padding-bottom of 10px.
> However, if later on, I create a rule telling that the ul will have a margin
> top of 5px... (because almost all may have that attribute) if I place the h2
> on top
Hello all,
I have just finished the wireframes phase for this project, and now the
designer is creating the final layouts for each of those pages.
I must develop the CSS for those 100 pages and I'm really afraid about
the fact that, I will have, almost surely, rules that will overwrite
each
>I was wondering what is best<
You already know this could be a Ford vs. Chevy post, but here is what time
has taught me. Unorganized is not the way to go. It will cost you even
during the initial development if it isn't organized. This is what shook
out from my experience:
A, I have one main
Personally, I tried once method 2 and lately had to repent for it,
because I kept going forward and backward in the file to change the
rules or to find a mistake etc.
I'm not an expert web developer, but recently I approached another
method involving more files. I prefer to have a basic file for
May I add:
Method 4:
/* Header styles */
div#header {
/* all header related styles, making no distinction between of
layout and typography */
}
div#header img {
/* style rules for the logo */
}
/* Navigation */
...
/* Content area */
...
/* Footer */
...
I personally find this to be m
Paul Hanson wrote:
> #Method3 - have to change 1 files, un-organized .posts{
> color: orange; background-color: black;
> font-size: 1em; font-family:Verdana, Arial, Helvetica, sans-serif;
> float:left; width: 200px; }
>
> I was wondering what is best, for a quick job, i'd probably do #3; but
> f
Cool thanks. I think I'll stick to 1 file and separate by areas on the page
(generic/basic rules for page; nav, header, content, mainContent, sidebar,
footer, etc). Sometimes I get the rule that applies to generic things like a
hyperlink in nav, header, content areas, so im not sure where to group
Or...
Just use some comments to explain what each file does.
If your reason for splitting things up is valid, then share the reasons and
explain.
The next person may think you are smart and write sexy code.
And you know, "chicks dig sexy code".
- dstefani
On Tue, 17 Jul 2007 13:18:17 -0400, Arian Hojat wrote:
> I have been looking at some tutorials. and some recommend the usual 'split
> into
> basic.css, typography.css, layout.css, colors.css, etc', but I can see a few
> peoples'
> arguments that to make a change for 1 thing, you might be looking
One thing to consider for your 3rd idea is that if you have to pass the
project off to someone else, the other two methods require the new
person to understand your logic and why you split things up into
multiple files. This could lead to frustration on their part if they
don't fully understand wha
I have been looking at some tutorials. and some recommend the usual 'split
into basic.css, typography.css, layout.css, colors.css, etc', but I can see
a few peoples' arguments that to make a change for 1 thing, you might be
looking at changing alot of files. For example, when you want do change
lay
20 matches
Mail list logo
