On Wednesday, March 27, 2002, at 06:01 , Daniel Rall wrote: >> I agree. We just need to figure out how to easily integrate any local >> changes we make to the stylesheets. Right now I've just mark the local >> modifications in the stylesheet.
One approach to consider is to keep your local mods in a separate stylesheet, link to it separately from your html head, *after* the links to the 'canonical' stylesheets, and let the cascade handle it. It could get a little more complicated than that in a few cases (certain additions/overrides will be easier than others, and then there are the Nav4-suicide-prevention techniques to preserve), but nothing insolubly so as far as I can imagine. Upside of course is that you needn't modify the sheets from s.t.o, and your mods are easy to track. Also, if your mods are generally popular, they might eventually be folded into the base styles. We might break the s.t.o stylesheets into several modules to avoid sending, say, Scarab-specific styles to Eyebrowse, and use the multiple-link method above to avoid having to do server-side CSS processing. > I checked in a versioned ZIP file to Scarab and Eyebrowse CVS and > integrated expansion of that ZIP file into their builds. This is a > good start, but it might be better to use a the style of updates that > Scarab uses for Turbine and its sub-projects. sounds nifty >> Also, Todd said the version in CVS is not the most recent and that you >> could update it for us. > > As soon as he checks in the updates to Style CVS, I can do so. SourceCast head has the latest, and did at the time of Daniel's initial check-in to Style. Not sure where the disconnect was/is. Meanwhile I am slowly, timorously learning to deal with style.tigris.org directly, as befits its owner (I suppose). Still queasy with CVS. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
