On 2/2/06, Troy Brophy <[EMAIL PROTECTED]> wrote: > This worked great up until I hit line 6000 of the > external CSS doc and Dreamweaver started choking a little each time I saved.
I'm surprised you waited so long! > Then I began grouping pages of the site into sections and creating CSS docs > for each section. This helped, because a lot of rules could be taken out of > the main doc and put into a smaller doc. (The server gzips all outgoing CSS > docs, so even with 6000 lines, the file size for transmission is only about > 10-15k.) I'm wondering why you didn't do this: give each page 2 CSS files, one for layout and the other for colors/typography, on top of the one site-wide CSS file. 3 stylesheets is a good division for each page. > Now, when a product manager points to an element on a page and says, "I'd > like you to move that box a little closer to the one above it," I first have > to open the HTML (actually .JSP) file, find the element in question, grab > the class name, then open the associated CSS doc, search for the class name > and finally make the change. (And of course, the requests are seldom so > simple, which means the fixes tend to involve a lot more scrolling around > inside a multi-thousand-line doc looking for a CSS value.) Does this mean you aren't using the FIND tool? I don't see the difficulty here. > So my current consideration is to move the specific positioning information > back into inline styling. Positioning that is repeated frequently on one > page will be moved to the header (internal). And, naturally, globally-used > styles will remain in the blessed external CSS docs. I really don't see why you need to do this. Have you ever worked with a large application written in a programming language? You have everything spread out over lots of small files. Then you work on those files in an editor that allows you to load them all up at once and search across all files. If you are going to do CSS at this scale, then you have to treat it the same way. I say if your process is cumbersome, then maybe you aren't using the right tools (software). Why do I recommend that you avoid inline styles? Because of two reasons: - it's harder to track inheritance, and fix inheritance errors, when you have 3 layers of your CSS, external/internal/inline, as opposed to just one. - it's hard to make sure you don't declare something twice, and on the magnitude of the application you are working with, this could happen a lot. The decision is up to you, of course, but it definitely sounds to me like you would benefit more from other ways of streamlining the process. -- -- Christian Montoya christianmontoya.com ... rdpdesign.com ... cssliquid.com ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d IE7b2 testing hub -- 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/
