Sample library.css file: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
Line 29: Line 29:
== Classes and Selectors ==
== Classes and Selectors ==


The <tt>library.css</tt> file relies on a class that is specific to the collection. The name of the class-- in this case, <tt>dictionary</tt>-- is set by the <tt>class</tt> field in the [[Sample_library.info_file|library.info file]].
; <tt>.dictionary</tt> :

:''In our dynamically-generated-everything future, you shouldn't have to include the class name in this file (provided that it's included in the library.info file instead). For now, though, you need to include it here, too.


; <tt>.dictionary a.entry:hover</tt> :
; <tt>.dictionary a.entry:hover</tt> :

Revision as of 22:09, 16 July 2007

Here is a sample library.css file a collection called Dictionary:

/* Style sheet for "Dictionary" collection--------------- */

.dictionary a.entry:hover {
	background: #F2DBA2;
	text-decoration: none;
}

.dictionary .metadata > .title {
	color: #DE801A;
}

.dictionary a {
	color: #DE801A;
	text-decoration: none;
}

.dictionary a:hover {
	text-decoration: underline;
}

.dictionary h1, .dictionary h2, .dictionary h3, .dictionary h4, .dictionary h5 {
	background: #F78F1E;
}

Classes and Selectors

The library.css file relies on a class that is specific to the collection. The name of the class-- in this case, dictionary-- is set by the class field in the library.info file.

In our dynamically-generated-everything future, you shouldn't have to include the class name in this file (provided that it's included in the library.info file instead). For now, though, you need to include it here, too.
.dictionary a.entry:hover
.dictionary .metadata > .title
.dictionary a
.dictionary a:hover
.dictionary h1, .dictionary h2, .dictionary h3, .dictionary h4, .dictionary h5