Arc-39-theme/HACKING.md

This theme uses node-sass/libsass to process the various .scss files. Never edit any of the .css files manually.

#### Editing the CSS based themes in the `common` directory (cinnamon, gnome-shell, gtk-3.0)

* Edit the `common/*/sass/*.scss` files

* Run `make` to generate all css files using sassc (starting with version 20180114). Gulp is no longer required.

--

#### Editing the GTK 2 themes

* Go to `common/gtk-2.0`

* The colors and includes are defined in `light/gtkrc`, `dark/gtkrc` and `darker/gtkrc` for each theme variant

* `main.rc` contains the major part of the theme

* `panel.rc` contains the panel styling for Xfce and MATE

* `apps.rc` contains some application specific rules

Because this theme is heavily based on the pixmap engine, a lot of the styling comes from the images in the `light/assets` and `dark/assets` folders. Don't edit these images directly. See the next section.

--

#### Editing the images for the GTK 2 and GTK 3 themes

* Go to the `common/gtk-2.0/light`, `common/gtk-2.0/dark`, or `common/gtk-3.0/$gtk-version` directory.

* Open the `assets.svg` file in inkscape. Each object in the .svg file corresponds to an image in the `assets` folder.

* Find the object you want to edit and make your changes. Important: Don't change the object id!

* Save `assets.svg` and run `make` (or `make -j$(nproc)` if you're in a hurry) from a terminal in the parent directory.
remove duplicate files 2016-04-05 16:19:46 +02:00			`This theme uses node-sass/libsass to process the various .scss files. Never edit any of the .css files manually.`

			#### Editing the CSS based themes in the `common` directory (cinnamon, gnome-shell, gtk-3.0)

			* Edit the `common//sass/.scss` files

Update HACKING.md to reflect sassc change 2018-01-09 19:07:17 +01:00			* Run `make` to generate all css files using sassc (starting with version 20180114). Gulp is no longer required.
remove duplicate files 2016-04-05 16:19:46 +02:00
			`--`

			`#### Editing the GTK 2 themes`

			* Go to `common/gtk-2.0`

autotools fixes (#155) * Fix image path names in GTK+3 gresource files Turns out it cares about the whole path, not just the filename, even if you embed the pixdata. * Fix change_color.sh following autotools changes * Add --jobs option to change_color.sh to pass to make This defaults to nproc. * Update HACKING document following autotools changes * Note in README which engines require sassc, optipng, and inkscape 2018-10-21 12:53:45 +02:00			* The colors and includes are defined in `light/gtkrc`, `dark/gtkrc` and `darker/gtkrc` for each theme variant
remove duplicate files 2016-04-05 16:19:46 +02:00
			* `main.rc` contains the major part of the theme

Correct capitalization 2017-01-09 15:41:26 +01:00			* `panel.rc` contains the panel styling for Xfce and MATE
remove duplicate files 2016-04-05 16:19:46 +02:00
			* `apps.rc` contains some application specific rules

autotools fixes (#155) * Fix image path names in GTK+3 gresource files Turns out it cares about the whole path, not just the filename, even if you embed the pixdata. * Fix change_color.sh following autotools changes * Add --jobs option to change_color.sh to pass to make This defaults to nproc. * Update HACKING document following autotools changes * Note in README which engines require sassc, optipng, and inkscape 2018-10-21 12:53:45 +02:00			Because this theme is heavily based on the pixmap engine, a lot of the styling comes from the images in the `light/assets` and `dark/assets` folders. Don't edit these images directly. See the next section.
remove duplicate files 2016-04-05 16:19:46 +02:00
			`--`

			`#### Editing the images for the GTK 2 and GTK 3 themes`

autotools fixes (#155) * Fix image path names in GTK+3 gresource files Turns out it cares about the whole path, not just the filename, even if you embed the pixdata. * Fix change_color.sh following autotools changes * Add --jobs option to change_color.sh to pass to make This defaults to nproc. * Update HACKING document following autotools changes * Note in README which engines require sassc, optipng, and inkscape 2018-10-21 12:53:45 +02:00			* Go to the `common/gtk-2.0/light`, `common/gtk-2.0/dark`, or `common/gtk-3.0/$gtk-version` directory.
remove duplicate files 2016-04-05 16:19:46 +02:00
autotools fixes (#155) * Fix image path names in GTK+3 gresource files Turns out it cares about the whole path, not just the filename, even if you embed the pixdata. * Fix change_color.sh following autotools changes * Add --jobs option to change_color.sh to pass to make This defaults to nproc. * Update HACKING document following autotools changes * Note in README which engines require sassc, optipng, and inkscape 2018-10-21 12:53:45 +02:00			* Open the `assets.svg` file in inkscape. Each object in the .svg file corresponds to an image in the `assets` folder.
remove duplicate files 2016-04-05 16:19:46 +02:00
Fixed typo (#518) 2016-05-12 15:25:51 +02:00			`* Find the object you want to edit and make your changes. Important: Don't change the object id!`
remove duplicate files 2016-04-05 16:19:46 +02:00
autotools fixes (#155) * Fix image path names in GTK+3 gresource files Turns out it cares about the whole path, not just the filename, even if you embed the pixdata. * Fix change_color.sh following autotools changes * Add --jobs option to change_color.sh to pass to make This defaults to nproc. * Update HACKING document following autotools changes * Note in README which engines require sassc, optipng, and inkscape 2018-10-21 12:53:45 +02:00			* Save `assets.svg` and run `make` (or `make -j$(nproc)` if you're in a hurry) from a terminal in the parent directory.