Sample library.css file: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (Replacing page with 'Here is the default <tt>library.css</tt> file:')
(rv remove Category:Uncategorized (this was the only member) so it shows on special pages where it might get a real cat)
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Here is the default <tt>library.css</tt> file:
Here is a sample <tt>library.css</tt> file a collection called <tt>Dictionary</tt>:

<pre>
/* 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;
}
</pre>

== 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>-- should also be recorded in the <tt>class</tt> field of the [[Sample_library.info_file|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.

See [[library.css]] for a description of classes and selectors.

Latest revision as of 04:16, 20 March 2008

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-- should also be recorded in the class field of 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.

See library.css for a description of classes and selectors.