gtk2/gtk/theme/Adwaita
Daniel Boles 70198e21ee themes: Make disabled Expander arrow look disabled
If GtkExpander:sensitive was FALSE, the arrow still got the normal fg
colour, which made it look clickable, in contrast to the adjacent label.
Fix this by adding selectors to catch the applicable :disabled states.

Note: Needing these may indicate an oops in generic styles elsewhere,
but I couldn’t see any, so let’s just get it looking right for now.

Close https://gitlab.gnome.org/GNOME/gtk/issues/146
2018-03-29 21:23:50 +01:00
..
assets Adwaita: Add scaled version of bullets and checks 2017-10-28 15:20:11 -04:00
_colors-public.scss Adwaita: export yet another named color for insensitive bg/fg... 2016-07-24 18:04:51 +02:00
_colors.scss Adwaita: color tweaks 2016-04-22 14:44:59 +02:00
_common.scss themes: Make disabled Expander arrow look disabled 2018-03-29 21:23:50 +01:00
_drawing.scss adwaita: Remove outlines from focused entries for now 2017-09-29 09:23:56 +02:00
assets.svg Adwaita: update assets svg 2016-10-05 11:35:47 +02:00
assets.txt
gtk-contained-dark.css themes: Make disabled Expander arrow look disabled 2018-03-29 21:23:50 +01:00
gtk-contained-dark.scss
gtk-contained.css themes: Make disabled Expander arrow look disabled 2018-03-29 21:23:50 +01:00
gtk-contained.scss
gtk-dark.css
gtk.css
meson.build meson: Rebuild the SCSS-based themes if sassc is available 2017-06-01 14:56:32 +01:00
parse-sass.sh Adwaita: add a sassc based parse-sass.sh script 2017-05-03 17:31:50 +02:00
README Rebuild CSS on all SCSS file changes 2017-04-01 16:19:54 +01:00
render-assets.sh Recover assets rendering script 2017-05-02 12:37:36 +01:00

Summary
-------

* Do not edit the CSS directly, edit the source SCSS files
* To be able to use the latest/adequate version of sass, install sassc
* The configure script will detect whether or not you have sassc installed;
  if you do, it will regenerate the CSS every time you modify the SCSS files.

How to tweak the theme
----------------------

Adwaita is a complex theme, so to keep it maintainable it's written and
processed in SASS. The generated CSS is then transformed into a gresource file
during gtk build and used at runtime in a non-legible or editable form.

It is very likely your change will happen in the _common.scss file. That's where
all the widget selectors are defined. Here's a rundown of the "supporting"
stylesheets, that are unlikely to be the right place for a drive by stylesheet
fix:

_colors.scss        - global color definitions. We keep the number of defined
                      colors to a necessary minimum, most colors are derived
                      from a handful of basics. It covers both the light variant
                      and the dark variant.

_colors-public.scss - SCSS colors exported through gtk to allow for 3rd party
                      apps color mixing.

_drawing.scss       - drawing helper mixings/functions to allow easier
                      definition of widget drawing under specific context. This
                      is why Adwaita isn't 15000 LOC.

_common.scss        - actual definitions of style for each widget. This is
                      where you are likely to add/remove your changes.
                      
You can read about SASS at http://sass-lang.com/documentation/. Once you make
your changes to the _common.scss file, GTK+ will rebuild the CSS files.