Ford, Mike wrote:
> On 04 June 2009 19:09, PJ advised:
>
>
>> Nitsan Bin-Nun wrote:
>>
From my experience I tend to use a difference ID for the
>> body tag, for
>>
>>> instance and then format it in my CSS using ID
>>> reference: #homepage .classname {
>>> col
Peter Ford wrote:
> PJ wrote:
>
>> tedd wrote:
>>
>>> At 3:58 PM -0400 6/4/09, PJ wrote:
>>>
tedd wrote:
> Style sheets are meant simplify things so decide on how you want
> things to look uniformly throughout your site and then stick with it.
>
On 04 June 2009 19:09, PJ advised:
> Nitsan Bin-Nun wrote:
>>> From my experience I tend to use a difference ID for the
> body tag, for
>> instance and then format it in my CSS using ID
>> reference: #homepage .classname {
>> color: blue;
>> }
>>
>> This way you can use a default format fo
At 10:23 AM +0100 6/5/09, Peter Ford wrote:
PJ wrote:
> tedd wrote:
>> First you figure out a layout, then you populate it. You don't pick a
>> layout, populate it and then change the layout.
>>
If only it were that simple.
When one is developing, one is always changing. And even when you'
At 4:54 PM -0400 6/4/09, PJ wrote:
tedd wrote:
> That's simply an example of not thinking things out before you write
the code.
First you figure out a layout, then you populate it. You don't pick a
> layout, populate it and then change the layout.
>
>
If only it were that simple.
When on
PJ wrote:
> tedd wrote:
>> At 3:58 PM -0400 6/4/09, PJ wrote:
>>> tedd wrote:
>>>
>>> > Style sheets are meant simplify things so decide on how you want
things to look uniformly throughout your site and then stick with it.
There's really no good reason to keep changing things throughou
tedd wrote:
> At 3:58 PM -0400 6/4/09, PJ wrote:
>> tedd wrote:
>>
>> > Style sheets are meant simplify things so decide on how you want
>>> things to look uniformly throughout your site and then stick with it.
>>> There's really no good reason to keep changing things throughout a
>>> site.
>>>
At 3:58 PM -0400 6/4/09, PJ wrote:
tedd wrote:
> Style sheets are meant simplify things so decide on how you want
things to look uniformly throughout your site and then stick with it.
There's really no good reason to keep changing things throughout a site.
Cheers,
tedd
Maybe I'm just
tedd wrote:
> At 2:08 PM -0400 6/4/09, PJ wrote:
>> Nitsan Bin-Nun wrote:
>>> >From my experience I tend to use a difference ID for the body tag,
>>> for
>>> instance and then format it in my CSS using ID
>>> reference:
>>> #homepage .classname {
>>>color: blue;
>>> }
>>>
>>> This wa
At 2:08 PM -0400 6/4/09, PJ wrote:
Nitsan Bin-Nun wrote:
>From my experience I tend to use a difference ID for the body tag, for
instance and then format it in my CSS using ID
reference:
#homepage .classname {
color: blue;
}
This way you can use a default format for all the pages
Nitsan Bin-Nun wrote:
> >From my experience I tend to use a difference ID for the body tag, for
> instance and then format it in my CSS using ID
> reference:
> #homepage .classname {
> color: blue;
> }
>
> This way you can use a default format for all the pages and create minor (or
> major)
>From my experience I tend to use a difference ID for the body tag, for
instance and then format it in my CSS using ID
reference:
#homepage .classname {
color: blue;
}
This way you can use a default format for all the pages and create minor (or
major) changes in the theme in no time :)
I w
Andrew Ballard wrote:
> On Thu, Jun 4, 2009 at 12:54 PM, PJ wrote:
>> This may not be strictly php but I think is may be relevant.
>> Were I to use a different css file for every page (that is slightly
>> different), would that affect performance?
>> It seems to me that might be a way of simplifyi
On Thu, Jun 4, 2009 at 12:54 PM, PJ wrote:
> This may not be strictly php but I think is may be relevant.
> Were I to use a different css file for every page (that is slightly
> different), would that affect performance?
> It seems to me that might be a way of simplifying and certainly speeding
>
14 matches
Mail list logo
