@charset "iso-8859-1";

/*******************************************************************************
*  tank.css : 2005.09.01
* -----------------------------------------------------------------------------
*  
*******************************************************************************/

@import "http://webhost.bridgew.edu/etribou/layouts/rMenu/rMenu.css";
@import "http://webhost.bridgew.edu/etribou/layouts/utility_css/dropmenu.css";

/* begin with generic selectors so that they can be overridden if needed
 * by classes deeper in the stylesheet
 */
.clear
{
	clear: both;
	padding-bottom: 1px;	/* for Gecko-based browsers */
	margin-bottom: -1px;	/* for Gecko-based browsers */
}
* html .clear
{
	padding: 0;
	margin: 0;
}
.hide
{
	display: none !important;
}
.inside
{
	/* glitch in IE caused by vertical padding in this class, so 0 padding is
	 * set here and those blocks that need the vertical padding must be 
	 * applied to the parent element. the purpose of this class is to provide
	 * horizontal padding without using hacks to get around IE's broken box 
	 * model. so it's okay to apply vertical padding to the parent element, 
	 * just not horizontal padding.
	 */
	padding: 0 14px;
}

/* The core Tank! layout structure begins here. No surprises here. Basic
 * negative margins (skidoo) layout structure with the added benefit of
 * forcing #pageWrapper to go the full height of the viewport even if the
 * content isn't tall enough to otherwise foce that height.
 *
 * Theme-related stuff (colors, fonts, etc...) are in the tank_theme.css
 * stylesheet, although 'default' values could be included within this
 * stylesheet.
 */
html, body
{
	height: 100%;	/* need to set the height on these two elements to 100%,
			   otherwise child elements such as #pageWrapper, when
			   its height is set to 100%, will only go as height as
			   the needed to contain the content within the 
			   element */
}
body
{
	margin: 0;
	padding: 0;	/* no padding here, we put it as margin values on 
			   #pageWrapper. padding/margin values here will break
			   the min-width emulation for IE */
} 
#pageWrapper
{
	border: solid 1px #000;
	border-width: 0 1px;
	margin: 0 20px 0 140px;	/* this value defines the margins surrounding the
				   layout and how much of the body element's 
				   background color will show through. since we're
				   using a 100% height hack, vertical margins don't
				   belong here */
	min-width: 700px;
	width: auto;
	min-height: 100%;
	_height: 100%;	/* if we didn't use the hack, and just set height to 100%
			   then some browsers will stop the #pageWrapper block
			   at 100% the height of the window. any content that
			   doesn't fit within that space will overflow but the
			   background colors of the columns will not carry. Ugly. */
}
* html #pageWrapper
{
	word-wrap: break-word;	/* invalid CSS but keeps IE from breaking 
				   horribly under narrow viewports */
}
#masthead
{
	padding: 10px;
	border-bottom: solid 1px #000;
}
#masthead h1, #masthead h2
{
	margin: 0;
	padding: 0;
}
#outerColumnContainer
{
	border-right: solid 16em #fff;
	z-index: 1;
}
#innerColumnContainer
{
	border-right: solid 1px #000;
	margin: 0 -1px 0 0;	/* -1px to make room for the 1px border. this is not
				   part of the negative margins hack used to create
				   multiple columns. */
	width: 100%;
	z-index: 2;
}
#contentColumn, #rightColumn
{
	float: left;
	overflow: visible;
	/* \*/ position: relative;	/* drop-down menus go transparent if this is 
					   left in for IE/Mac to see. Very odd. */
}
#rightColumn
{
	margin: 0 -16em 0 1px;
	width: 16em;
}
#contentColumn
{
	margin-right: -1px;
	width: 100%;
}
* html #contentColumn
{			/* * html #rightColumn */
	overflow: hidden;	/* this is because IE 6 and earlier do not handle overflow
				   properly. visible overflow forces the overflowing block
				   to grow to contain the oversized child element. this can
				   break the layout. so we hide content. */
}
#rightColumn h3
{
	position: relative;
	z-index: 999;
}
* html #rightColumn h3
{
	display: inline-block;
}
#footer
{
	border-top: solid 1px #000;
	text-align: center;
}
#footer p
{
	/* #footer is also assigned the .inside class so padding is being 
	 * applied already. we don't need the paragraph gutterspace on top 
	 * of it. since the footer is only one paragraph, we can just kill 
	 * all gutterspace on all p elements in #footer. but if you plan on 
	 * having more than one p element, go ahead and kill this rule and 
	 * remove the .inside class assignment from #footer in the HTML
	 */
	padding: 0;
	margin: 0;
}

/* twoColumns class for implementing a simple 2-column structure wherever you need it
 * inside the content column. 
 */
div.twoColumns
{
	margin: 14px 0;
	width: 100%;
}
div.twoColumns div.leftColumn, 
div.twoColumns div.rightColumn
{
	float: left;
	width: 50%;
	overflow: visible;	/* fix for IE italics bug */
}
div.twoColumns div.leftColumn
{
	margin-right: -1px;
	border-right: solid 1px #000;
}
div.twoColumns div.rightColumn
{
	margin-right: -2px;
	border-left: solid 1px #000;
}
div.twoColumns div.leftColumn div.inside
{
	padding-left: 0;
}
div.twoColumns div.rightColumn div.inside
{
	padding-right: 0;
}

/* Miscellaneous things layout-related, but not core to the layout itself.
 */
p.fontsize-set, div.colorPicker
{
	_padding-top: 1px;	/* keep IE from putting in too much padding */
	text-align: center;
}
p.fontsize-set img
{
	border-width: 0;
	margin: 0 3px;
}
div.colorPicker a
{
	display: block;
	width: 12px;
	height: 12px;
	margin: 0 5px;
	float: left;
	padding: 0;
	line-height: 0;
	font-size: 0;
	background-color: #dc8;	/* default color picker */
}

/* style-switcher will use anchors converted to block elements with no
 * content. set the background-color property to whatever value that particular
 * swatch should be
 */
a#colorPicker-blue
{
	background-color: #abe;
}
a#colorPicker-green
{
	background-color: #aca;
}
a#colorPicker-camille
{
	background-color: #e77;
}
a#colorPicker-gray
{
	background-color: #ccc;
}
a#colorPicker-black
{
	background-color: #000;
}

/******************************************************************************/

@charset "iso-8859-1";

/*******************************************************************************
*  tank_base_theme.css : 2005.09.01
* -----------------------------------------------------------------------------
*  Base Tank! theme. Applied to the layout by default. Theme modifications
*  applied via a style-switcher or external stylesheet should build upon what
*  is here. 
*******************************************************************************/

@import "http://webhost.bridgew.edu/etribou/layouts/utility_css/visual_consistencies.css";

p
{
	line-height: 140%;
}
body
{
	background-color: #fec;
	color: #000;
	background-image: url("../images/ruthsarian.png");
	background-repeat: no-repeat;
	background-position: 30px 100%;
	background-attachment: fixed;
}
#topMenu ul
{
	width: 12em;	/* make the pop menus a little wider */
}
#pageWrapper, #innerColumnContainer, #masthead, #footer, #topMenu, #topMenu ul, #topMenu a
{
	border-color: #c93;
}
div.twoColumns div.leftColumn, div.twoColumns div.rightColumn
{
	border-color: #ddd;
}
#pageWrapper
{
	background-color: #f9f9f2;
	color: #665;
	font-family: arial, helvetica, sans-serif;
	font-size: 80%;
	background-image: url("../images/ruthsarian.png");
	background-repeat: no-repeat;
	background-position: -110px 100%;
}
#masthead
{
	background-color: #dc8;
	background-image: url("../images/tank.png");
	background-position: 100% 100%;
	background-repeat: no-repeat;
	padding: 10px;
	color: #000;
}
#masthead h1
{
	font-size: 150%;
}
#masthead h2
{
	font-size: 260%;
	color: #862;
}
#outerColumnContainer
{
	background-color: #fff;
	color: #223;
	border-right-color: #fff; /* right column background color */
}

#contentColumn, #rightColumn, #masthead, #footer
{
	padding-top: 10px;
	padding-bottom: 10px;
}
#contentColumn
{
	padding-top: 0;
}
#topMenu
{
	border: solid 0 #c93;
	border-width: 4px 0 0 0;
	padding-right: 40px;
}
#topMenu li a, #topMenu li a:link, #topMenu li a:visited, #topMenu li a:active
{
	background-color: #ffe;
}
#topMenu li a:hover
{
	color: #fff;
	background-color: #c93;	/* keep the same color as the borders */
}
#rightColumn ul.rMenu
{
	margin: 0 5px 10px 5px;
}
#rightColumn ul.rMenu, #rightColumn ul.rMenu li a,  #rightColumn ul.rMenu li ul
{
	border-color: #ed9;
}
#rightColumn ul.rMenu a:link, #rightColumn ul.rMenu a:visited, #rightColumn ul.rMenu a:active
{
	background-color: #ffe;
	color: #336;
}
#rightColumn ul.rMenu a:hover
{
	background-color: #c93;
	color: #fff;
}
#rightColumn h3
{
	margin-bottom: 0;
	padding-bottom: 0;
	color: #b83;
	z-index: 999;
	line-height: 0.75em;
	font-size: 140%;
	/* \*/ position: relative;	/* With this here, IE/Mac will put this on 
					   top of every other element in the page. so
					   drop-down menus appear under. ick. so hide
					   it with this hack. */
}

@charset "iso-8859-1";

/*******************************************************************************
*  rMenu.css : 2006.10.17 : ruthsarian@gmail.com
* ------------------------------------------------------------------------------
* Ruthsarian Menus - A CSS-based dropdown menu system
*
* <insert long, boring ramble here>
*
* KNOWN BUGS
*	- Opera 7.23 and earlier have problems with absolutely positioned 
*	  elements positioned relative to a parent element. this causes a
*	  problem with right-aligned horizontal menus. stay away from those
*	  types of menus if you've got any reason to care about Opera 7.23 or
*	  earlier versions.
*
* DEV NOTES
*	- setting position: relative; to ul.rMenu triggers a bug in Netscape 7
*	  and earlier that makes content jump as menus pop
*	- need to remember that when assigning multiple classes to an element
*	  to list them left-to-right from most-specific to least-specific.
*	  Otherwise IE/Mac flips out
*	- IE/Mac needs whitespace before <UL> and </UL> tags in the markup
*	  otherwise very odd things can happen
*	- hasLayout should not be triggered on LI elements under IE7
*	- IE/Mac has a selector bug where rMenu-v* and rMenu-h* rules
*	  are applied to rMenu-v and rMenu-h elements. ie rMenu-vRight rules
*	  get applied to rMenu-v elements. This is incorrect.
*	- if any parent element of the menu is a float it (or the parent of
*	  the menu) needs to be relatively positioned. Otherwise the menu
*	  is not rendered on the page.
*
* EXAMPLE HTML
*	<ul class="rMenu-hor rMenu"
*	  ><li
*	    ><a href="">Menu Item</a
*	    > <ul class="rMenu-ver"
*	      ><li
*	        ><a href="">Menu Item</a
*	      ></li
*	      ><li
*	        ><a href="">Menu Item</a
*	      ></li
*	    > </ul
*	  ></li
*	  ><li
*	    ><a href="">Menu Item</a
*	  ></li
*	 > </ul>
*
* ------------------------------------------------------------------------------
*  This stylesheet is released into the public domain.
*******************************************************************************/

/*******************************************************************************
 * General Menu Mechanics
 *
 * Below is a set of rules which is applicable to any list used within
 * this dropdown menu system. You could apply just these rules and get
 * a basic dropdown menu system working just fine in FireFox, Opera,
 * Safari, and most other modern browsers.
 */
ul.rMenu, ul.rMenu ul, ul.rMenu li, ul.rMenu a
{
	display: block;		/* make these objects blocks so they're easier
				   to deal with */
	margin: 0;
	padding: 0;		/* get rid of padding/margin values that these
				   elements may have by default */
}
ul.rMenu, ul.rMenu li, ul.rMenu ul
{
	list-style: none;	/* proper browsers don't require this because
				   block elements (see previous rule set) cannot
				   take any list-style property. meaning 
				   existing list-style properties are removed
				   when they are set to display: block. IE7 
				   seems to ignore this fact under certain
				   situations so we explicitly set it here
				   even though it's, technically, incorrect 
				   CSS (but it will validate). */
}
ul.rMenu ul
{
	display: none;		/* hide the sub-menus until needed */
	position: absolute;	/* remove the sub-menus from the flow of the
				   layout so when they pop they don't cause any
				   disfiguration of the layout */
}
ul.rMenu li
{
	position: relative;	/* so sub-menus position relative to their 
				   parent LI element */
}
ul.rMenu li:hover
{
	z-index: 999;		/* make sure this and any sub-menus that pop 
				   appear above everything else on the page */
}
ul.rMenu li:hover > ul
{
	display: block;		/* show the sub-menu */
}

/*******************************************************************************
 * Extended Menu Mechanics
 *
 * These rules exist only for specific menu types, such as horizontal or
 * vertical menus, right or left aligned menus.
 */
ul.rMenu-hor li
{
	float: left;
	width: auto;
}
ul.rMenu-hRight li
{
	float: right;		/* horizontal, right menus need their LI
				   elements floated to get them over there */
}
ul.rMenu-ver li
{
	float: none;		/* clear this so vertical sub-menus that are
				   children of horizontal menus won't have
				   their LI widths set to auto. */
}
ul.rMenu-ver, ul.rMenu-ver ul
{
	width: 10em;		/* sub-menus need a defined width, especially
				   vertical sub-menus. salt to taste. */
}
ul.rMenu-wide
{
	width: auto;		/* apply this rule if you want the top-level
				   menu to go as wide as possible. this is 
				   something you might want if your top-level
				   is a vertical menu that spans the width
				   of a column which has its width 
				   pre-defined. */
}
ul.rMenu-vRight
{
	float: right;		/* use this to float a vertical menu right. */
}
ul.rMenu-lFloat
{
	float: left;		/* use this to float a vertical menu left. */
}
ul.rMenu-noFloat
{
	float: none;		/* this is to cover those cases where a menu
				   is floated by default and you have a reason
				   to not float it. such as a menu on the
				   right side of the screen that you want 
				   to have drops going left but not floated.
				   to be honest, i don't think this rule is 
				   needed. the clearfix hack will resolve
				   renering issues associated with a floated
				   menu anyways. */
}

/*******************************************************************************
 * DROP POSITIONS
 *
 * This handles where sub-menus drops relative to the parent element. The same
 * attributes should be set in all rule sets in this section so that cascading
 * rules don't create problems.
 */
ul.rMenu-hor ul
{
	top: auto;		/* a value of 100% creates a problem in IE 5.0 
				   and Opera 7.23 */
	right: auto;
	left: auto;		/* typically want a value of 0 here but set to
				   auto for same reasons detailed above */
	margin-top: -1px;	/* so the top border of the dropdown menu 
				   overlaps the bottom border of its parent
				   horizontal menu. */
}
ul.rMenu-ver ul
{
	left: 60%;
	right: auto;
	top: auto;
	margin-top: -0.5em;	/* i prefer top: 80% but this creates a problem
				   in iCab so negative top margin must be used.
				   salt to taste. */
}
ul.rMenu-vRight ul, ul.rMenu-hRight ul.rMenu-ver ul
{
	left: -60%;
	right: auto;
	top: auto;
	margin-top: -0.5em;	/* i prefer top: 80% but this creates a problem
				   in iCab so negative top margin must be used.
				   salt to taste. */
}
ul.rMenu-hRight ul
{
	left: auto;
	right: 0;		/* this doesn't work in Opera 7.23 but 7.5 and
				   beyond work fine. this means right-aligned
				   horizontal menus break in Opera 7.23 and
				   earlier. no workaround has been found. */
	top: auto;
	margin-top: -1px;	/* so the top border of the dropdown menu 
				   overlaps the bottom border of its parent
				   horizontal menu. */
}

/*******************************************************************************
 * PRESENTATION : General
 *
 * This is where the visual presentation of the menu is handled. If you try to
 * alter the borders width or location of placement pay close attention to the
 * notes provided with the existing CSS rules in this section. There are key
 * reasons behind borders and negative margins being placed where they are.
 */
ul.rMenu li a
{
	border: solid 1px #99f	/* border around all anchor tags */
}
ul.rMenu-hor li
{
	margin-bottom: 0;	/* remove any negative bottom margin if the
				   horizontal menu is child of a vertical 
				   menu */
	margin-left: -1px;	/* negative borders on LIs to make borders on
				   child A elements overlap. they go here and
				   not on the A element for compatibility
				   reasons (IE6 and earlier) */
}
ul.rMenu-h
{
	padding-left: 1px ;	/* compensate for the 1px left jog created by
				   the above negative margin. */
}
ul.rMenu-ver li
{
	margin-left: 0;
	margin-top: -1px;	/* same thing above except for vertical
				   menus */
}
ul.rMenu-ver
{
	border-top: solid 1px #fff;	/* ditto */
}
ul.rMenu li a
{
	padding: 2px 5px 3px;	/* 2px top, 3px bottom always seems to
				   provide the most visually balanced 
				   padding */
}
ul.rMenu li a:link, ul.rMenu li a:hover, ul.rMenu li a:visited, ul.rMenu li a:active
{
	text-decoration: none;
}
ul.rMenu li.sfhover a:active,
ul.rMenu li:hover a:active
{
	color: #fff;
	background-color: #c00;
}
ul.rMenu li
{
	background-color: #ddf;	/* default background color of menu items */
}
ul.rMenu li:hover,
ul.rMenu li.sfhover
{
	background-color: #eda;	/* background color for parent menu items of
				   the current sub-menu. includes the sfhover
				   class which is used in the suckerfish hack
				   detailed later in this stylesheet. */
}
ul.rMenu li a:hover
{
	background-color: #ffc;
}

/*******************************************************************************
 * PRESENTATION : Expand
 *
 * the bits below implement a graphic to appear on those anchor elements which 
 * have the rMenu-expand class assigned. this is something you have to do
 * manually on any LI element containing a UL element that is to be a dropdown 
 * menu. there is no mechanism to do this automatically.
 *
 * the seemingly redundant CSS is done for reasons similar to the suckerfish
 * css. it's to deal with all sorts of nested menu issues. it'll work as far
 * as three levels deep, after that all bets off.
 */
ul.rMenu li.rMenu-expand a,
ul.rMenu li.rMenu-expand li.rMenu-expand a,
ul.rMenu li.rMenu-expand li.rMenu-expand li.rMenu-expand a
{
	padding-right: 25px;
	background-image: url("expand-right.gif");
	background-repeat: no-repeat;
	background-position: 100% 50%;
}
ul.rMenu-vRight li.rMenu-expand a,
ul.rMenu-vRight li.rMenu-expand li.rMenu-expand a,
ul.rMenu-vRight li.rMenu-expand li.rMenu-expand li.rMenu-expand a,
ul.rMenu-hRight li.rMenu-expand a,
ul.rMenu-hRight li.rMenu-expand li.rMenu-expand a,
ul.rMenu-hRight li.rMenu-expand li.rMenu-expand li.rMenu-expand a
{
	padding-right: 5px;
	padding-left: 20px;
	background-image: url("expand-left.gif");
	background-repeat: no-repeat;
	background-position: -5px 50%;
}
ul.rMenu-hor li.rMenu-expand a
{
	padding-left: 5px;	/* reset padding */
	padding-right: 15px;
	background-image: url("expand-down.gif");
	background-position: 100% 50%;
}
ul.rMenu li.rMenu-expand li a,
ul.rMenu li.rMenu-expand li.rMenu-expand li a,
ul.rMenu li.rMenu-expand li.rMenu-expand li.rMenu-expand li a
{
	background-image: none;
	padding-right: 5px;	/* reset padding */
	padding-left: 5px;	/* reset padding */
}

/*******************************************************************************
 * HACKS : General
 *
 * These are rules specifically targeted to resolve bugs/quirks that some
 * browser exhibit.
 */
* html ul.rMenu
{
	display: inline-block;	/* this is for IE/Mac. it forces IE/Mac to 
				   expand the element's dimensions to contain 
				   its floating child elements without a 
				   clearing element. */
	/* \*/ display: block;	/* override above rule for every other 
				   browser using IE/Mac backslash hack */
	position: relative;	/* IE 5.0/Mac needs this or it may clip the
				   dropdown menus */
	/* \*/ position: static;/* reset position attribute for IE/Win as it
				   causes z-index problems */
}
* html ul.rMenu ul
{
	float: left;		/* IE/Mac 5.0 needs this and IE/Win 6 and earlier
				   don't show any problems with applying this 
				   rule. */
}
ul.rMenu ul
{
	background-color: #fff;	/* IE/Win (includeing 7) needs this on an object 
				   that hasLayout so that it doesn't "look through"
				   the menu and let any object (text) below the 
				   menu to gain focus, causing the menu to 
				   disappear. application of this rule does not
				   cause any rendering problems with other browsers
				   as the background color his covered by the
				   menu itself. */
}
* html ul.rMenu-ver li,
* html ul.rMenu-hor li ul.rMenu-ver li
{
				/* the second selector in this rule is there 
				   because of problems IE/Mac has with 
				   inheritance and what rules should take
				   precedence. and to serve as a reminder on
				   how to work around the issue if it's 
				   encountered again down the road. */
	width: 100%;
	float: left;
	clear: left;		/* IE6 (and earlier?) stick space below any LI
				   in :hover state with a sub-menu. floating
				   the LIs seems to work around this issue. But
				   note that this also triggers hasLayout 
				   because we need a width of 100% on floats.
				   But hasLayout on LIs breaks the menu in IE7.
				   So we really need to be careful not to let
				   floats get into anything other than IE6
				   and earlier. IE Mac seems to need this
				   too for some other reason. */
}
ul.rMenu-ver li a
{
	min-width: 0;		/* trigger hasLayout for IE7 on anchor 
				   elements. without hasLayout on anchors
				   they would not expand the full width 
				   of the menu. this rule may not trigger
				   hasLayour in later versions of IE and
				   if you find this system broken in new
				   versions of IE, this is probably the
				   source. */
}
* html ul.rMenu-ver li a
{
	height: auto;		/* triggers hasLayout for IE/Mac */
	/* \*/ height: 100%;	/* trigger hasLayout for IE6 and earlier. does
				   not work for IE7 */
}
* html ul.rMenu-h
{	/* hide from IE Mac \*/
	padding-left: 2px;	/* IE6 and earlier double the negative margins
				   on the LI elements of horizontal menus. this
				   is because the LIs float but the parent
				   isn't floating. this can be fixed by floating
				   rMenu-hor but I'd rather not float it so I just
				   double up the padding used to compensate. */
}
* html ul.rMenu-hor li
{
	width: 6em;		/* IE Mac doesn't do auto widths so specify a width 
				   for the sake of IE/Mac. Salt to taste. */
	/* \*/ width: auto;	/* now undo previous rule for non Macs by using 
				   the IE Mac backslash comment hack */
}

/*******************************************************************************
 * HACKS : Suckerfish
 *
 * IE6 and earlier do not support the :hover pseudoclass and so javascript is 
 * used to add the "sfhover" class of any LI element that the mouse is currently 
 * over. This method is called suckerfish and you can read up on it at:
 * http://www.htmldog.com/articles/suckerfish/dropdowns/
 *
 * NOTE: this allows for support of dropdown menus up to 3 levels deep. if you 
 *	 want to support greather menu depth you need to alter these selectors. 
 *	 read the above mentioned website for more info on how to do that.
 */
* html ul.rMenu li.sfhover
{
	z-index: 999;
}
* html ul.rMenu li.sfhover ul ul, 
* html ul.rMenu li.sfhover ul ul ul
{ 
	display: none;		/* IE/Suckerfish alternative for browsers that
				   don't support :hover state on LI elements */
}
* html ul.rMenu li.sfhover ul, 
* html ul.rMenu li li.sfhover ul, 
* html ul.rMenu li li li.sfhover ul
{
	display: block;		/* ^ ditto ^ */
}

/*******************************************************************************
 * HACKS : Clearfix
 *
 * Clearfix provides a means to for an element to contain all it's floated 
 * children even if it's not normally tall enough to do so. For more information
 * on clearfix please see:
 * http://www.positioniseverything.net/easyclearing.html
 */
.clearfix:after
{
    content: "."; 
    display: block; 
    height: 0; 
    clear: both; 
    visibility: hidden;
}
.clearfix
{
	min-width: 0;		/* trigger hasLayout for IE7 */
	display: inline-block;
	/* \*/	display: block;	/* Hide from IE Mac */
}
* html .clearfix
{
	/* \*/  height: 1%;	/* Hide from IE Mac */ 
}

/******************************************************************************/

@charset "iso-8859-1";

/*******************************************************************************
*  visual_consistencies.css : 2005.09.07 : Ruthsarian Layouts
* -----------------------------------------------------------------------------
*  Font sizes on heading elements and the margin/padding applied to these
*  same elements will vary from browser to browser. This is an attempt to pull
*  the font sizes and spacing together for a consistent look across all
*  browsers. 
*
*  There are other rules included in this stylesheet (with comments on each)
*  to handle other visual consistency issues. You do not need to use this
*  stylesheet, nor do you need to follow it exactly. You can make changes
*  anywhere you want to make things look the way you want to. Nothing here
*  _should_ break a layout if modified.
*******************************************************************************/

ul, ol, dl, p, h1, h2, h3, h4, h5, h6
{
	/* pixels are used here, rather than ems, because I want a consistent 
	 * margin on the different headings. if I use ems, 1em for an h1 element 
	 * is much larger than 1em on an h6 element. I don't want this.
	 */
	margin-top: 10px;
	margin-bottom: 10px;
	padding-top: 0;
	padding-bottom: 0;
}
ul ul, ul ol, ol ul, ol ol
{
	/* kill margins on sub-lists
	 */
	margin-top: 0;
	margin-bottom: 0;
}
h1
{
	font-size: 240%;
}
h2
{
	font-size: 180%;
}
h3
{
	font-size: 140%;
}
h4
{
	font-size: 100%;
}
h5
{
	font-size: 70%;
}
h6
{
	font-size: 50%;
}
a, a:link, a:visited, a:active
{
	text-decoration: underline;
}
a:hover
{
	/* because I like the visual feedback a user gets when they
	 * mouse over a link and see the underline of the link
	 * disappear.
	 */
	text-decoration: none;
}
code, pre
{
	/* Make sure we're all using the same monospaced font for CODE
	 * and PRE elements
	 */
	font-family: "Courier New", Courier, monospace;
}
label
{
	/* It's all about the visual feedback. In this case, label 
	 * elements are usually clickable which then set focus on
	 * their target. I want to show that to the user in a manner
	 * they are used to and understand.
	 */
	cursor: pointer;
}
table
{
	/* Some browsers won't carry the font size down into the 
	 * browser like they're suppose to.
	 */
	font-size: 100%;
}
td, th
{
	/* I never like or use the default vertical centering "feature"
	 * provided by tables. 
	 */
	vertical-align: top;
}
body
{
	/* I've seen several comments that setting the base font size to 100.1%
	 * fixes some browser bugs. Which bugs? I don't know. I believe it's
	 * to fix some rounding-error bugs that some browsers (Mozilla) are
	 * prone to. It doesn't hurt anything, so I keep it here.
	 */
	font-size: 100.1%;
}

/******************************************************************************/

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
	"http://www.w3.org/TR/html4/strict.dtd">

<html lang="en">
	<head>
		<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
		<style type="text/css" media="screen">
		<!--
			@import "css/tank.css";
			@import "css/tank_base_theme.css";
		-->
		</style>
		<link rel="alternate stylesheet" title="blue : color" href="css/theme/blue.css" media="screen">
		<link rel="alternate stylesheet" title="green : color" href="css/theme/green.css" media="screen">
		<link rel="alternate stylesheet" title="camille : color" href="css/theme/camille.css" media="screen">
		<link rel="alternate stylesheet" title="gray : color" href="css/theme/gray.css" media="screen">
		<link rel="alternate stylesheet" title="black : color" href="css/theme/black.css" media="screen">
		<script type="text/javascript" src="http://webhost.bridgew.edu/etribou/layouts/javascript/ruthsarian_utilities.js"></script>
		<script type="text/javascript">
		<!--
			var font_sizes = new Array( 100, 86, 124 );
			var current_font_size = 0;
			var browser = new browser_detect();
 			if ( ( typeof( NN_reloadPage ) ).toLowerCase() != 'undefined' ) { NN_reloadPage( true ); }
			if ( ( typeof( set_min_width ) ).toLowerCase() != 'undefined' ) { set_min_width( 'pageWrapper' , 760 ); }
			if ( ( typeof( sfHover       ) ).toLowerCase() != 'undefined' ) { event_attach( 'onload' , function () { sfHover( 'topMenu' ); sfHover( 'rightMenu' ); } );  }
			if ( ( typeof( loadFontSize  ) ).toLowerCase() != 'undefined' ) { event_attach( 'onload' , loadFontSize ); }
			if ( ( typeof( setActiveStyleSheet ) ).toLowerCase() != 'undefined' ) { setActiveStyleSheet( getPreferredStylesheet( 'color' ) , 'color' ); }
		//	if ( ( typeof( opacity_init  ) ).toLowerCase() != 'undefined' ) { opacity_init(); }
		//-->
		</script>
		<title>Tank! : Ruthsarian Layouts</title>
	</head>
	<body lang="en">
		<div id="pageWrapper">
			<div id="masthead">

<h1>Ruthsarian Layouts</h1>
<h2>Tank!</h2>

				<hr class="hide">
			</div>
			<div id="outerColumnContainer">
				<div id="innerColumnContainer">
					<div id="contentColumn">

	<ul id="topMenu" class="clearfix rMenu-hRight rMenu-hor rMenu"
		><li class="rMenu-expand"
			><a href="http://webhost.bridgew.edu/etribou/layouts/">Layouts</a
			> <ul class="rMenu-ver"
				><li class="rMenu-expand"
					><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/">Skidoo</a
					> <ul class=""
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/fixed_width.html">Fixed Width</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/fluid_width.html">Fluid Fixed Width</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/tweak_02.html">Detached Masthead</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/tweak_01.html">Border Into Masthead</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/bgImages.html">Background Images</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo/demos/gutterless.html">Gutterless</a
						></li
					> </ul
				></li
				><li
					><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo_too/">Skidoo Too</a
				></li
				><li
					><a href="http://webhost.bridgew.edu/etribou/layouts/skidoo_too/gargoyles/">Gargoyles</a
				></li
				><li class="rMenu-expand"
					><a href="http://webhost.bridgew.edu/etribou/layouts/exp/index.html">Experiments</a
					> <ul class=""
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/exp/plaine/">Plaine</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/exp/nausicaa/">Nausicaä</a
						></li
						><li
							><a href="http://webhost.bridgew.edu/etribou/layouts/exp/bob/">Bob</a
						></li
					> </ul
				></li
			> </ul
		></li
		><li
			><a href="http://webhost.bridgew.edu/etribou/software/">Labs</a
		></li
		><li class="rMenu-expand"
			><a href="http://weblog.bridgew.edu/ruthsarian/">Blog</a
			> <ul class="rMenu-ver"
				><li
					><a href="http://weblog.bridgew.edu/ruthsarian/archives/cat_web_of_information.html">Web of Information</a
				></li
				><li
					><a href="http://weblog.bridgew.edu/ruthsarian/archives/000130.html">Wide Images in CSS Layouts</a
				></li
				><li
					><a href="http://weblog.bridgew.edu/ruthsarian/archives/000105.html">IE Boxing</a
				></li
			> </ul
		></li
		><li
			><a href="mailto:ruthsarian@gmail.com">Contact</a
		></li
	> </ul>

						<div class="inside">

<div class="twoColumns">
	<div class="leftColumn">
		<div class="inside">

<h3>Introduction</h3>
<p>
	<em>Tank!</em> is CSS-based web page layout. The goal for this layout
	was to incorporate several tricks/features that help further demonstrate
	the versatility of CSS. These include drop-down menus, theme switching,
	changing font size, source ordering, transparent images, multiple columns, 
	and hopefully some nice style.
</p>

<h3>A Work In Progress</h3>
<p>
	I'm releasing this layout a little early. It's still a work in progress.
	IE 5.0 (for Mac OS 9 and earlier) has some severe bugs that cause the text
	to not appear correctly; however IE 5.2 works just fine. Netscape 7.0 has
	a problem with the drop-down menus where they are displayed in the flow
	of the document, forcing the rest of the page's content down while the
	drop-menu is displayed. There is no Netscape 4 specific stylesheet
	at the moment. NS4 users will simply see a plain page. Oh, and if you
	figure out my not-completely-documented dropdown system and try to
	apply it to the vertical menu, you may run into some problems, so I 
	wouldn't try it right now.
</p>
<p>
	Feel free to send an e-mail to <em>ruthsarian at gmail dot com</em>
	if you find other bugs that you'd like to report.
</p>

<h3>No Zip (Yet)</h3>
<p>
	I'm not yet providing an archive of the layout with all the necessary
	CSS and JavaScript and all the paths worked out, etc.. in a single ZIP
	ready to go. This is because I don't consider this layout to be
	ready <em>enough</em>. If you want to take this layout for a test drive,
	you'll have to figure out how to pull out the CSS, HTML and JavaScript
	needed. This isn't hard at all, but if you don't know how then you probably
	aren't ready to use a layout that may still be a bit... touchy.
</p>

<h3>Short on documentation</h3>
<p>
	I'll try to add more documentation to this page as I have time. Right now
	I'm focusing in on the more important pieces of information about this layout,
	rather than worry about a full write-up on all the intricacies.
</p>

		</div>
	</div>
	<div class="rightColumn">
		<div class="inside">

<h3>Gargoyles - Season 2, Vol. 1</h3>
<p>
	<a href="http://www.amazon.com/gp/product/B000ATQYVA/">Gargoyles - Season 2, Volume 1</a>
	was released on December 6, 2005. The DVD contains the first half (26 half-hour episodes) of 
	the second seasion of <a href="http://tv.disney.go.com/jetix/gargoyles/">Gargoyles</a>. Special
	features include commentary on the 4-part "City of Stone", a featurette on the making of with
	new interviews of several cast members, and introductions of each episode by creator
	<a href="http://www.s8.org/gargoyles/askgreg/">Greg Weisman</a>.
</p>

<h3>Support / Donations</h3>
<p>
	Every so often I hear from someone who offers to make a donation or asks
	about ways to support my work. My position, as outlined in the content of 
	the <a href="http://webhost.bridgew.edu/etribou/layouts/skidoo_too/gargoyles/index.html">Skidoo 
	Too: Gargoyles</a> layout, remains the same: I don't want money. I'm not trying to make money, 
	I just want to share with others my own bits of	work with CSS. I think the knowledge I gain 
	from my own work is its own reward (regardless of how corny that sounds).
</p>
<p>
	However, if you would like to support a cause near and dear to me, I
	would ask that you pick up a copy of <a href="http://www.amazon.com/gp/product/B000ATQYVA/">Gargoyles 
	- Season 2, Volume 1</a>. Gargoyles is a great show, well written, and entertaining
	to both kids and adults. I would like to see the show continued in some manner, but to
	do that we need to first get <a href="http://www.disney.com">Disney's</a> attention. That
	can be done through increasing salse of the latest <a href="http://www