Comments on: Minimizing css files http://flanders.co.nz/2007/07/04/minimizing-css-files/ thoughts.each { &:propagandise } Sun, 08 Jan 2012 14:53:43 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Ivan Porto Carrero http://flanders.co.nz/2007/07/04/minimizing-css-files/comment-page-1/#comment-5 Ivan Porto Carrero Wed, 04 Jul 2007 11:00:53 +0000 http://blog.koolkraft.net/2007/07/04/minimizing-css-files/#comment-5 I agree that there is more that can be done. <br />I chose for this approach of doing it at runtime with caching because it allows for the css person to create separate files keeping his stuff organized without having too much of a deployment hassle.<br />I try to maintain xcopy deployment which means that I don't want any extra steps except just copying the files to the webserver and probably changing the connection string and application runtime mode.<br />If I would have to start scripting a complete deployment script that's when deployment has the potential to evolve into a nightmare.<br />Look at ruby deployment which is easily qualified as a less than optimal experience.<br />One of the strong points of .net is that there is a web.config file in which you can quickly change the behaviour of your application.<br />I could for example add a config property that disables the minifying if some errors occur.<br /><br />That's mostly why I chose for an @ run-time version. I agree that there is more that can be done.
I chose for this approach of doing it at runtime with caching because it allows for the css person to create separate files keeping his stuff organized without having too much of a deployment hassle.
I try to maintain xcopy deployment which means that I don’t want any extra steps except just copying the files to the webserver and probably changing the connection string and application runtime mode.
If I would have to start scripting a complete deployment script that’s when deployment has the potential to evolve into a nightmare.
Look at ruby deployment which is easily qualified as a less than optimal experience.
One of the strong points of .net is that there is a web.config file in which you can quickly change the behaviour of your application.
I could for example add a config property that disables the minifying if some errors occur.

That’s mostly why I chose for an @ run-time version.

]]> By: Adam http://flanders.co.nz/2007/07/04/minimizing-css-files/comment-page-1/#comment-4 Adam Wed, 04 Jul 2007 10:37:36 +0000 http://blog.koolkraft.net/2007/07/04/minimizing-css-files/#comment-4 Nice.<br /><br />I'd prefer processing it when I deploy, rather an at request time (even if it is cached).<br />This would give you greater control over the delivered control, as you can test locally far easier.<br /><br />What I really want to do sometime (if I ever have a free weekend) is write something that will refactor the rules - so join disparate styles, sort the properties (color, background, font, ..etc), and minimise (probably onto one line rules for deployments sake - but no more, gzip will can do that while keeping the code readable) Nice.

I’d prefer processing it when I deploy, rather an at request time (even if it is cached).
This would give you greater control over the delivered control, as you can test locally far easier.

What I really want to do sometime (if I ever have a free weekend) is write something that will refactor the rules – so join disparate styles, sort the properties (color, background, font, ..etc), and minimise (probably onto one line rules for deployments sake – but no more, gzip will can do that while keeping the code readable)

]]>