gtk-css-engine r142 - in trunk: . doc

[robsta svn gnome org]

Author: robsta
Date: Wed Oct  1 08:45:29 2008
New Revision: 142
URL: http://svn.gnome.org/viewvc/gtk-css-engine?rev=142&view=rev

Log:
* doc/01-introduction.txt: update.


Modified:
   trunk/ChangeLog
   trunk/doc/01-introduction.txt

Modified: trunk/doc/01-introduction.txt
==============================================================================
--- trunk/doc/01-introduction.txt	(original)
+++ trunk/doc/01-introduction.txt	Wed Oct  1 08:45:29 2008
@@ -7,9 +7,15 @@
 
 While the GNOME theming scene is thriving with exciting projects like Aurora, Clearlooks and Murrine, application developers and designers are increasingly concerned [#evil1]_ [#evil2]_ [#evil3]_ [#evil4]_ about the sustainability of the current concept involving a theme engine providing a set of styling options, and a gtkrc [#gtkrc]_ file specifying colours and fine-tuning engine-behaviour. A somewhat obvious alternative approach is to put all styling information into the configuration file and provide a single theme engine that is powerful enough to satisfy the designers' demand. This is where `CSS <http://www.w3.org/TR/CSS21/>`_ comes into play. CSS already works well making millions of web-pages look good, the *gtk-css-engine* project is about making a some of its features available for applications using the Gtk+ toolkit. However, an application window containing menus, toolbars, buttons and text entry fields is not exactly the same as a web-page, so it is worthwile dis
 cussing how to work around the impedance mismatch.
 
-So what is required for Gtk+ to work with CSS? Let us first look at the elements that Gtk+ makes available for theming. At the lowest level there is a number of basic building blocks, the so-called *primitives* (arrow, horizontal line, vertical line, checkmark. etc. see `below <#Primitives>`_ for an exhaustive list).
+So what is required for Gtk+ to work with CSS? Let us first look at the elements that Gtk+ makes available for theming. At the lowest level there is a number of basic building blocks, the so-called *primitives* (arrow, horizontal line, vertical line, checkmark. etc. see `below <#Primitives>`_ for an exhaustive list). All widgets are drawn using those primitives, a GtkButton for example consists of a ``box`` element for border and background, and a ``layout`` element drawn on top of it, showing the button's text label. So much for theory, more about there relation between primitives and widgets in a minute. The following example shows how to do theme a simple button.
+::
 
+	GtkButton {
+		background-color: red;
+		border: 1px solid black;
+	}
 
+Theming a button is pretty straight forward, a scrollbar on the other hand 
 
 
 Appendix