Hi *, On Sun, Mar 27, 2005 at 11:16:30AM +0300, Miikka Leskinen wrote: > [...] > It would be fun to troubleshoot this, but it will take some extra hours > because of the over-over-overriden CSS issue. To be honest, I still > don't understand why there needs to be so many of them.
> People here have > been talking something about SourceCast and tigris, but I'm not > completely sure what they are (something to do with the CollabNet > company). SourceCast is the WebHosting platform (the product), CollabNet the company. > But in any case, it's a problem imho. There are loads of CSS > after CSS without any clear categorization. inst.css and tigris.css are there to override the defaults of Sourcecast. These are already modified on the current OOo-site so we copied them to the staging server to have the state of current www.openoffice.org to work with. overrides.css is used to track the changes that are needed compared to the current live (www.openoffice.org) site. Once the problems are sorted out the file will be merged to the inst and tigris files inst.css and tigris.css contain styles for dynamically generated parts of the various servlets/types of pages you encounter on www.openoffice.org (issueZilla, tables, mailinglists, account-manager, etc. This is another reason why a seperate overrides.css is used: Make the changes seperate, make it easy to identify the elements you're messing with. But again: this is only meant as a temporary solution. Once the problems are sorted out, these will be merged with the other files again. style.css contains the styles that are used by the frontpage. To sum up: If www.openoffice.org works properly, then inst.css and tigris.css are not responsible for the brokeness. Since the toptabs, banner and footer were changed from tables to other elementtypes, the old styles aren't applied anyway. (and as written before, the elements of the frontpage itself (everything supposed to be below the top-navbar and above the footer) are handled in styles.css) A single file with all the styles ain't more structured than different files. The contrary is the case. You'd spend most of the time scrolling/identifying the style that is responsible for the element. ciao Christian -- NP: sleepingodslie - Babylon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
