gtk2/gtk/theme/Adwaita/README

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
  and rebuild GTK+.

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 form 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.
Adwaita: provide simple guidelines for theming - Some simple instructions for future SASS/ruby lovers 2014-09-29 12:07:10 +00:00			`Summary`
			`-------`

Adwaita/README: Update to reflect we use sassc now We moved from the Ruby compiler to sassc in commit 67953e9cfb5dec4a509525fd572c3d21c38d8cff, so this copies across the updated info about building from GTK+ 4. Also, explain the purpose of parse-sass.sh, since while that is not mentioned in GTK+ 4 – and perhaps does not need to be, thanks to Meson – we are still on Autotools here, and rebuilding the entirety of GTK+ 3 if you only edited the CSS is a lot of waiting for no good reason. 2017-10-08 12:59:30 +00:00			`* 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`
Adwaita/README: Don’t bother mentioning parse-sass Assume no one wants to make a change without testing it in GTK+… If anyone has a reason to do this, they’ll be able to figure it out. 2017-10-08 13:07:29 +00:00			`and rebuild GTK+.`
Adwaita: provide simple guidelines for theming - Some simple instructions for future SASS/ruby lovers 2014-09-29 12:07:10 +00:00
			`How to tweak the theme`
			`----------------------`

Adwaita: Fix a few typos in README 2015-08-30 19:12:35 +00:00			`Adwaita is a complex theme, so to keep it maintainable it's written and processed in SASS. The`
Adwaita/README: Don’t bother mentioning parse-sass Assume no one wants to make a change without testing it in GTK+… If anyone has a reason to do this, they’ll be able to figure it out. 2017-10-08 13:07:29 +00:00			`generated CSS is then transformed into a GResource file during GTK+ build and used at runtime in a`
Adwaita: provide simple guidelines for theming - Some simple instructions for future SASS/ruby lovers 2014-09-29 12:07:10 +00:00			`non-legible or editable form.`

Adwaita: selectors cleanup and some refactoring 2014-10-02 18:40:18 +00:00			`It is very likely your change will happen in the _common.scss file. That's where all the widget`
Adwaita: provide simple guidelines for theming - Some simple instructions for future SASS/ruby lovers 2014-09-29 12:07:10 +00:00			`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 form 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.`

Adwaita/README: Update to reflect we use sassc now We moved from the Ruby compiler to sassc in commit 67953e9cfb5dec4a509525fd572c3d21c38d8cff, so this copies across the updated info about building from GTK+ 4. Also, explain the purpose of parse-sass.sh, since while that is not mentioned in GTK+ 4 – and perhaps does not need to be, thanks to Meson – we are still on Autotools here, and rebuilding the entirety of GTK+ 3 if you only edited the CSS is a lot of waiting for no good reason. 2017-10-08 12:59:30 +00:00			`You can read about SASS at http://sass-lang.com/documentation/. Once you make`
Adwaita/README: Don’t bother mentioning parse-sass Assume no one wants to make a change without testing it in GTK+… If anyone has a reason to do this, they’ll be able to figure it out. 2017-10-08 13:07:29 +00:00			`your changes to the _common.scss file, GTK+ will rebuild the CSS files.`