95b2104301
Replace themes with new ones from https://github.com/hhhorb/bunsen-themes-dev Move themes from root dir to "themes". debian/control: add Recommends: gtk3-nocsd, change Depends: libgtk-3-0 (>= 3.22.11) debian/copyright: Update dates |
||
---|---|---|
.. | ||
.sass-cache | ||
apps | ||
assets | ||
_colors-public.scss | ||
_colors.scss | ||
_common.scss | ||
_drawing.scss | ||
_gnome-apps.scss | ||
_lightdm-gtk-greeter.scss | ||
_unity.scss | ||
_xfce.scss | ||
Gemfile | ||
Gemfile.lock | ||
gtk-contained.css | ||
gtk-contained.scss | ||
gtk.css | ||
gtk.gresource.xml | ||
parse-sass.sh | ||
README | ||
settings.ini |
Summary ------- * Do not edit the CSS directly, edit the source SCSS files and process them with SASS (run `./parse-sass.sh` when you have the required software installed, as described below) * To be able to use the latest/adequate version of sass, install ruby, gem, sass & bundle. On Fedora F20, this is done with `sudo dnf install rubygems && gem install bundle && bundle install` from the same directory this README resides in. How to tweak the theme ---------------------- Greybird is a complex theme (based on Adwaita), so to keep it maintainable it's written and processed in SASS. 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, you can either run the ./parse-sass.sh script or keep SASS watching for changes as you edit. This is done by running `bundle exec sass --watch --sourcemap=none .` If sass is out of date, or is missing, you can install it with `bundle install`.