proposal #1

Closed
wants to merge 1 commit into
from

Conversation

Projects
None yet
2 participants

hlibco commented Apr 27, 2011

Alphabetically ordered elements properties. It helps developers/designers teams to maintain the code and prevent redeclarations.

Alphabetically ordered elements properties. It helps developers/desig…
…ners teams to maintain the code and prevent redeclarations.
Owner

csswizardry commented Apr 27, 2011

Hi,
Thanks for this, however I am firmly opposed to ordering CSS alphabetically and always have been.

Ordering CSS alphabetically would be like organising your CD collection by how bright the covers are—it is ordered, but not by anything meaningful.

Also, we write in x,y format (that is to say ‘background-position:left top;’ etc) but alphabetised puts height (y) before width (x).

Furthermore, this (logical, ordered) CSS:

position:absolute;
top:0;
right:0;
bottom:0;
left:0;

would become:

bottom:0;
left:0;
position:absolute;
right:0;
top:0;

Thanks for the input but I’m afraid I don’t see alphabetised CSS making its way into inuit.css any time soon.

Best,
Harry

hlibco commented Apr 27, 2011

Hi, Harry.

I agree with you when talking about write CSS in logical order, but when
we talk about maintenance it's a little bit different.

Let me explain what I'm talking about:

When you write code, you do this in a logical way (I take your point, you
are right!), but later when you should change some properties values, you
don't do this in a "logical" way, you wanna go straight to the point...

You know you want to change "font-size" value, so, alphabetically, you go
directlly to "F" and find "font-size", without needing to read all element
properties until find it. That's the why Firebug ordered all properties
alphabetically.

I think you should take this into consideration, once you already have the
code written, is just to re-order things. I created a Fork and do this
modifications, if you want to integrate it to the trunk I think it can be
useul for other people.

There are some other points I think you can improove:

1 - Why don't you have a different stylesheet to "debug"? like
inuit.debug.css?

If I'm working on development environment, I include it, otherwise, I don't.

*2 - Why don't you have one .css for each screen resolution? *
You know, some mobile devices can't cache files over 25kb, and the framework
is going go be heavy.
You can add these .css via Javascript ( http://adapt.960.gs/ ), some people
say it's not a good idea using conditional inclusions.

3 - Why don't you use separate stylesheet to style Logo, Nav and other
elements?

Thanks for the great job and I really appreciate to contribute with this
project.

Best regards,

--Felipe Hlibco

On Wed, Apr 27, 2011 at 7:08 PM, csswizardry <
reply@reply.github.com>wrote:

Hi,
Thanks for this, however I am firmly opposed to ordering CSS alphabetically
and always have been.

Ordering CSS alphabetically would be like organising your CD collection by
how bright the covers are—it is ordered, but not by anything meaningful.

Also, we write in x,y format (that is to say ‘background-position:left
top;’ etc) but alphabetised puts height (y) before width (x).

Furthermore, this (logical, ordered) CSS:

position:absolute;
top:0;
right:0;
bottom:0;
left:0;

would become:

bottom:0;
left:0;
position:absolute;
right:0;
top:0;

Thanks for the input but I don’t see alphabetised CSS making its way into
inuit.css any time soon.

Best,
Harry

Reply to this email directly or view it on GitHub:
#1 (comment)

sweetroll referenced this pull request in sweetroll/inuit.css Nov 10, 2014

Merged in develop (pull request #1)
stripped unnecessary modules
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment