summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMatthias Clasen <mclasen@redhat.com>2011-01-30 23:53:19 -0500
committerMatthias Clasen <mclasen@redhat.com>2011-01-30 23:53:19 -0500
commitcfa6505504fab38107f40f42fcdc06f27f2c8439 (patch)
tree96154bba88ec35b633e11fc1b4020bd1d0365391 /docs
parent175c57ebd7d1f31aba855b8af491859f9203fa78 (diff)
downloadgtk+-cfa6505504fab38107f40f42fcdc06f27f2c8439.tar.gz
Mention key themes in the migration guide
Diffstat (limited to 'docs')
-rw-r--r--docs/reference/gtk/migrating-GtkStyleContext.xml10
1 files changed, 9 insertions, 1 deletions
diff --git a/docs/reference/gtk/migrating-GtkStyleContext.xml b/docs/reference/gtk/migrating-GtkStyleContext.xml
index e228a00e45..b2e73edc41 100644
--- a/docs/reference/gtk/migrating-GtkStyleContext.xml
+++ b/docs/reference/gtk/migrating-GtkStyleContext.xml
@@ -29,11 +29,19 @@
</para>
<para>
- If your theme gtkrc file was providing values for #GtkSettings, you
+ If your theme RC file was providing values for #GtkSettings, you
can install a <filename>settings.ini</filename> keyfile along with
the <filename>gtk.css</filename> to provide theme-specific defaults
for settings.
</para>
+
+ <para>
+ Key themes have been converted to CSS syntax too. See the
+ <link linkend="css-binding-set">GtkCssProvider</link> documentation
+ information about the syntax. GTK+ looks for key themes in the file
+ <filename>$datadir/themes/<replaceable>theme</replaceable>/gtk-3.0/gtk-keys.css</filename>, where <replaceable>theme</replaceable> is the current
+ key theme name.
+ </para>
</section>
<section id="gtk-migrating-theme-GtkStyleContext-engines">