Hi Oliver, Edward, Tee and Kepler Well, bummer. I was really hoping that @import (or some variant within a "base.css" sheet) would work (with various media type specifications) because on each project I've got like eight different css sheets that I link to my index.php (I can hear you guys laughing, crying, screaming).
I do keep everything separate for ease of maintenance/tweaking as time goes on. Obviously linking all of these sheets does have a proformance hit but I've never measured it against a single sheet but I find organizing my style sheets like this helps my work-related santity. Sort of strange that the technique I was trying to employ is mentioned as a viable solution on different sites (with the exception of the media problem with IE) but that's why - on questions like this - I like to vette an option like this to a group of working professionals on this group. Thanks so much for your opinions an insight. Kepler - I'll take a look at your free tool - greatly appreciate the link! Cole -----Original Message----- From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Kepler Gelotte Sent: Sunday, July 25, 2010 4:24 AM To: wsg@webstandardsgroup.org Subject: RE: [WSG] @import and IE7 > I agree that import doesnt perform too well. Separate the files in > whatever way will support the growth of your site best, and make sure > you use some sort of combine tool / filter to reduce the number of > requests Hi Cole, I have a free tool that will combine CSS files on the server using @include() instead of @import(). The CSS files are combined and compressed before being sent to the browser. You can then use <link media="..." /> as others have suggested to separate your print from screen stylesheets. The latest version also supports caching if you are concerned about performance. Just make sure you have a writable "cache" directory under your CSS folder(s). This all works dynamically by adding the files to your CSS directory(ies). One caveat, if you split your CSS files into subdirectories, make sure you copy the files to all folders that contain CSS. You can read/download it here: http://www.coolphptools.com/dynamic_css Best of luck to you. Best regards, Kepler Gelotte Neighbor Webmaster, Inc. 156 Normandy Dr., Piscataway, NJ 08854 www.neighborwebmaster.com phone/fax: (732) 302-0904 ________________________________________ From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Edward Lynn Sent: Saturday, July 24, 2010 4:44 AM To: wsg@webstandardsgroup.org Subject: Re: [WSG] @import and IE7 I agree that import doesnt perform too well. Separate the files in whatever way will support the growth of your site best, and make sure you use some sort of combine tool / filter to reduce the number of requests Ed On Sat, Jul 24, 2010 at 8:18 AM, Oliver Boermans <boerm...@gmail.com> wrote: Hi Cole On Saturday, July 24, 2010, Cole Kuryakin <c...@koisis.com> wrote: > Hello All - > > I've finally decided that I'd like to <link></link> a single base > style sheet (base.css) into my projects. > > The base.css would then @import various other style sheets which would > define the dclarations for project layout, type, color, forms, etc. I would not recommend you separate your CSS files for purely organisational purposes. Do this _within_ your files. Less files loaded by the browser means faster pagel loading. @import is also bad for performance. Where you must separate your files it is better to have multiple link elements. The other advantage of avoiding @import is to see what CSS is being loaded into the page it is only necessary to look in the HTML. This can save someone else a lot of time troubleshooting your site later. Before Firebug l would separate my CSS into a bunch of files, just to reduce the time to navigate them. Now the inspector in Firebug makes this so easy there isn't really a lot of organisation advantage in doing so. I hope this is helpful, even if I didn't really answer your question... Cheers Ollie @ollicle ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org ******************************************************************* ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
