Barney Carroll wrote: > Zoe M. Gillenwater wrote: > >> I may start breaking my sheets into very broad components in the future, >> based on the standard way I organize my one big sheet right now, but it >> would be very limited in scope. Right now I generally have these sheets: >> >> base.css (linked from all pages with no media setting, contains only >> body text and color settings for NN4 users) >> global.css (imported from base.css, contains all rules for all pages, >> organized heavily by my standard method) >> ie-hacks.css (conditional comment from all pages, contains hacks for all >> levels of IE, separated by star html hacks as needed) >> print.css (linked from all pages with print media setting, contains >> print styles to override rules in global.css) >> >> Zoe >> > > And of course, when you're partitioning by category the useful > distinctions mentioned above don't sit easy. > > Can I see myself having two levels of @import, ending print-layout.css > and handheld-presentation.css? The sad thing is, I can. > > I get your method generally, but don't understand why you want to > distinguish between base.css and global.css. Could global be renamed > screen.css? >
Not really, since its styles apply to both screen and print, and everything, since I don't specify a media type for either base.css or global.css. That way, my print sheet doesn't have to redeclare all my fonts and whatnot. Instead, I just override the stuff I don't want to happen in my print sheet. I've found this easier than the other way around. The reason I keep a base sheet is because I work for the government and still have some NN4 users. They get all styles hidden from them except those written directly in base.css, which as I said are only text and color settings on the body and links. At least the page isn't 100% unstyled for them and thus hopefully doesn't look "broken." The import within base.css for global.css is read by all modern browsers, so that's why it contains all my styles. Make more sense now? You can check out www.hsrc.unc.edu or www.saferoutesinfo.org if you want to see it in practice. Zoe -- Zoe M. Gillenwater Design Services Manager UNC Highway Safety Research Center http://www.hsrc.unc.edu ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7 information -- http://css-discuss.incutio.com/?page=IE7 List wiki/FAQ -- http://css-discuss.incutio.com/ Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
