[adwaita-icon-theme/meson] README



commit 14670f4d7e006a8d32f9d85d2d1681160242eba2
Author: Jakub Steiner <jimmac gmail com>
Date:   Wed Apr 6 09:50:51 2022 +0200

    README

 README.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)
---
diff --git a/README.md b/README.md
new file mode 100644
index 000000000..0f4e05447
--- /dev/null
+++ b/README.md
@@ -0,0 +1,27 @@
+# Adwaita Icon Theme
+![Adwaita Icons](src/logo.svg)
+
+## Bugs and Requests
+If you're a core GNOME application maintainer and you have an icon need that bridges multiple components or 
apps, feel free to file a request in the [issue 
tracker](https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues). If you're an application developer, 
file a request against the [Icon Development 
Kit](https://gitlab.gnome.org/Teams/Design/icon-development-kit/-/issues) instead.
+
+
+## Fullcolor vs symbolic
+For an up to date guide on how to use and how to design GNOME style icons, see the GNOME User Interface 
Guidelines: [UI Icons](https://developer.gnome.org/hig/guidelines/ui-icons.html) and [App 
Icons](https://developer.gnome.org/hig/guidelines/app-icons.html).
+
+## Building and Contributing to Adwaita
+No new additions should be made unless very thoroughly discussed. *a-i-t* is the wrong way to reuse icon 
assets (no API, false promise of stability). The very essential set of icon that *every* app is going to need 
goes to the toolkit. Apps ship their own assets. 3rd party developers can make use of a [growing library of 
icons](https://gitlab.gnome.org/Teams/Design/icon-development-kit) and request additional icons there. best 
way to look for icons is through the [Icon 
Library](https://flathub.org/apps/details/org.gnome.design.IconLibrary) app.
+
+While many legacy symbolics only live as the exported individual SVGS in `Adwaita/symbolic/`, the 
replacements are maintained in `src/symbolic/core.svg`. The contexts are [no longer 
used](https://gitlab.gnome.org/GNOME/adwaita-icon-theme/-/issues/73) and all icons go into `actions`. Please 
refer to the [Devkit guidelines](https://gitlab.gnome.org/Teams/Design/icon-development-kit) on how to 
structure the metadata.
+
+### Recoloring
+The color of the icon set is defined at runtime. Every single icon from the set is actually embedded inside 
an xml container that has a stylesheet overriding the colors.
+
+There is a couple of things the icon author needs to be aware of and a few things s/he can make use of. The 
stylesheet is setting the color of the fill for all rectangles and paths. **DO NOT** leave any rectangles or 
paths with no fill/stroke thinking it's invisible.
+
+Gtk doesn't care about the colors you define for the icon. They are recolored at runtime. If you need 
portions of icons to have a color, you need to include a `class` attribute to the shape or group and set it 
to one of the three values below. 
+
+- `warning` - this maps to gtk `@warning_color`
+- `error` - maps to `@error_color`
+- `success` - maps to `@success_color`
+
+[Symbolic Preview](https://flathub.org/apps/details/org.gnome.design.SymbolicPreview) doesn't convert 
strokes to paths yet, so you need to do it manually for now in Inkscape (`Path -> Stroke to Path`). 
Alternatively you can add Live path effect `join type` to your stroke and keep it non destructive.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]