SharePoint utilizes CSS quite heavily and it is both a express and a blessing. Since nearly all of the SharePoint 2003 UI is hard coded in the site definitions. CSS provides one of the best ways to update the UI. But the SharePoint CSS is also pretty unruly and can be quite daunting at first look. Let’s go ahead and get the numbers out on the table.
For a SharePoint 2003 Portal and WSS lay there are 7 separate call sheets (excluding themes) totaling to 7,403 lines of label and 1,227 style statements. Ouch! Luckily some of that we can slash off pretty quick. Four of the seven style sheets I have yet to ever undergo to edit to alter a place (Menu css. OWSmac css. OWSnocr css. Paystub css). The other three are pretty easy:
SPS css and OWS css have a few quirks. There are call selectors that are repeated in each. In some cases the reproduce styles are not connected and hold back WSS and Portal separately but in other cases the two are connected and what you have in one can possibly decree the other making for a confusing and frustrating situation. Additionally the styles may share the same selector but enumerate different properties in the declaration.
When a portal page is rendered it pulls in several style sheets in this request 1) OWS css; 2) MENU css; 3) SPS css.
When a WSS site is rendered it pulls in the OWS css call pelt and then the furnish call pelt if a furnish has been applied to a site.
The order of which the call sheets are called in the code is important. The way CSS works generally the measure property specified in a declaration for a selector is the property that is used for rendering the element. So if the same selector is in both SPS css and OWS css a portal will use the declaration listed in SPS css for the element because SPS css is called after OWS css in the code. This is the basis behind how themes bring home the bacon as well. In a furnish you only need to include updated declarations in the theme style sheet and when the place is rendered the new declarations in the furnish call pelt will override anything set in OWS css.
Editing the call sheets directly used by SharePoint requires adjust duplication of label and fast results but can cause maintenance issues further down the road. With any conjoin or upgrade you run the risk of losing your changes. Your changes would undergo to be reapplied as opposed to other approaches of just resynching up pointers to custom call sheets. The other hindrance is that the SharePoint style sheets are very long and the number of styles you ordain actually end up needing to edit ordain pale in comparison to the final statement ascertain in the files. So you ordain have to broach with a lot of finding of statements and wading through untouched statements. This is not the cleanest way to specify new styles.
Cruise 4 Cash -
Detective Sherlock -
Free Bid Auctions -
Expert Poker Tips -
Shop 4 Money
Win Any Lottery -
Repo Car Search -
Psychics 4 Free -
High Quality Games -
Driving 4 Dollars
Related article:
http://www.indelv.com/sharepoint-and-css.html
comments | Add comment | Report as Spam
|