Comments on: Coda and coding techniques

By: Phosphor

Phosphor — Tue, 03 Feb 2009 20:00:29 +0000

I have some syntax coloring themes for coda that I create on a regular basis if your interested. themes

By: lewro

lewro — Tue, 18 Nov 2008 06:19:50 +0000

@Mr.Fussyfont – thanks for that, I have fixed it immediately. My spelling is really not very good so I am happy you are helping me with that.

I am glad you like the site.

By: Mr. Fussyfont

Mr. Fussyfont — Tue, 18 Nov 2008 03:55:52 +0000

Just a tiny pet peeve of mine: Mac, as in Macintosh computer, is not an acronym, and thus should not be capitalized. MAC, as in MAC address, stands for Media Access Control. It also stands for other things in other contexts. That’s all.

BTW, nice site.

By: lewro

lewro — Sun, 16 Nov 2008 20:53:13 +0000

@Ash good to know, my previous line-manager was using the same approach. As I said before I do not mind any of these methods as long as the code is clean and readable. It all comes to personal preferences but I always like to do thinks right way and follow the rules. It’s just a pity there are no such rules for CSS yet.

I think there is a big space for standardization in our industry. Another example could be naming conventions where HTML 5 is bringing some useful stuff such are header, footer tags etc…

By: Ash

Ash — Sun, 16 Nov 2008 16:05:05 +0000

I follow a similar approach to Anthony when it comes to CSS. Everything in a single file and alter the layout of properties depending. I have been considering starting to use separate files though recently. I can see that there are advantages to it but it just seems like having everything in one file is so much easier to manage than splitting it over several.

By: lewro

lewro — Sun, 16 Nov 2008 12:00:12 +0000

@anthony – I like your site a lot and also the way you do your CSS. Its all very clear and easy to read. I think the biggest advantage of your approach (having it all properties in line for a single selector) is that you can very quickly scan through the whole CSS to find what you looking for.

My CSS file is lot longer but I use Firebug for debugging so I always know what line I need to change because I change it in Firebug first. I also use “=” sign for name of the sections so I can quickly search for them without getting results I do not want.

I actually like both CSS methods and still have not decided which to use in the future projects. I would really welcome some kind of standardization. If there are some rules set up by web standards group or w3c I would follow them.

By: Anthony Short

Anthony Short — Sun, 16 Nov 2008 03:15:23 +0000

I’ve tried out a few different approaches for my css, but I’ve found that single file css is still my favourite. When you use a lot of different files it can become tedious to find and edit the correct style.

Perhaps on extremely large sites I would use an individual css file for that page and another ‘main’ file.

I like using single line for selectors with only a couple of properties or are small sections, and multiline for main or large selectors.I personally don’t like indenting my css. But it’s all very subjective. :)

I divide the pages up by the body id and have a section with the varied layouts. It all very simple.

Without trying to spam my site, if you check out the css, that’s my latest format.