Module Skins

tanveerc edited this page Dec 26, 2013 · 5 revisions

Each of the three module types needs to be skinned differently. Abstracting all the heavy lifting to the mod, complex, and pop classes means that all of the values in the skins are predictable. In fact, I’ll show you how they can be easily calculated.

Extending mod

Let’s create a simple grey rounded corner box.

<div class="mod simple"> 
	<b class="top"><b class="tl"></b><b class="tr"></b></b> 
	<div class="inner">
		<div class="hd">
			<h3>simple</h3>
		</div>
		<div class="bd">
			<p>Body</p>
		</div>
	</div>
	<b class="bottom"><b class="bl"></b><b class="br"></b></b> 
</div>
/* ----- simple (extends mod) ----- */
.simple .inner {border:1px solid #D7D7D7;-moz-border-radius: 7px;-webkit-border-radius: 7px;border-radius: 7px;}
.simple b{*background-image:url(skin/mod/simple_corners.png);}
  1. We define the border to be one pixel solid gray. Anytime only one border is used it should be placed on inner rather than the module itself (to simplify the skin).
  2. We then tell browsers that the module should have rounded corners.
  3. Internet Explorer 5.5, 6, 7, 8 do not support rounded corners. Line two provides an image backup to generate these corners. The star hack is used so that better browsers that natively support rounded corners do not download the extra image unnecessarily. You may also choose to omit this line and provide a square corner fallback for IE depending on how much market share they have amongst your visitors.

complex

pop