ASCII text
1
Summary
2
-------
3
* Do not edit the CSS directly, edit the source SCSS files and process them with SASS (running
5
`make` should do that when you have the required software installed, as described below;
6
run `/.parse-sass.sh` manually if it doesn't)
7
* To be able to use the lates/adequate version of sass, install ruby, gem, sass & bundle.
8
On Fedora F20, this is done with `sudo dnf install rubygems && gem install bundle && bundle install`
9
from the same directory this README resides in.
10
How to tweak the theme
12
----------------------
13
Adwaita is a complex theme, so to keep it maintainable it's written and processed in SASS, the
15
generated CSS is then transformed into a gresource file during gtk build and used at runtime in a
16
non-legible or editable form.
17
It is very likely your change will happen in the _common.scss file. That's where all the widget
19
selectors are defined. Here's a rundown of the "supporting" stylesheets, that are unlikely to be the
20
right place for a drive by stylesheet fix:
21
_colors.scss - global color definitions. We keep the number of defined colors to a necessary minimum,
23
most colors are derived from a handful of basics. It is an exact copy of the gtk+
24
counterpart. Light theme is used for the classic theme and dark is for GNOME3 shell
25
default.
26
_drawing.scss - drawing helper mixings/functions to allow easier definition of widget drawing under
28
specific context. This is why Adwaita isn't 15000 LOC.
29
_common.scss - actual definitions of style for each widget. This is where you are likely to add/remove
31
your changes.
32
33
You can read about SASS at http://sass-lang.com/documentation/. Once you make your changes to the
34
_common.scss file, you can either run the ./parse-sass.sh script or keep SASS watching for changes as you
35
edit. This is done by running `bundle exec sass --watch --sourcemap=none .` If sass is out of date, or is
36
missing, you can install it with `bundle install`.
37