Any web server worth it's salt will gzip compress static files, which makes trimming all the whitespace a bit pointless. Ditto with any crazy-assed class naming scheme you come up with to make things smaller.
I learnt most of what I know about HTML, CSS & JS from viewing the source of pages that had something I thought was cool, so I think it's kinda nice to make my stuff as readable as possible for anyone doing the same these days. Also helps when I come back to make changes 6 months later & wonder WTF things do :) [EMAIL PROTECTED] wrote: > Does everyone else on the list do this? > > For the sake of 11k that is cached on the first page load it seems a > little drastic. I do programming work as well as markup and the > indentation/formatting of the code is very important in producing > readable code. If it was only me looking at the CSS then fine, but in > a team situation producing CSS formatted like this could make human > reading a lot harder and thus slow production time. > > I can understand if you use TopStyle to do this automatically but I > just thought a note of caution/consideration to others reading this > that may feel it's a thing all good CSS developers must do. > > Personally I'd prefer to leave my CSS formatted as is and shave the > k's off images used, etc. Then if I need to hand the stylesheets over > to someone they are more usable. > > Nick -- Lindsay Evans. Developer, Red Square Productions. [p] 8596.4000 [f] 8596.4001 [w] www.redsquare.com.au ***************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help *****************************************************
