ac3b3533d5
Now that the ::initiate signal may contain the PID of the initiating process, we can try to resolve it to an application and use that to indicate where a request originated. This should work for well-behaved applications that only ask for permissions in response to a user action, but unfortunately not when it would be most useful, that is when the dialog is triggered "out of nowhere" by a background service ... https://bugzilla.gnome.org/show_bug.cgi?id=688351 |
||
|---|---|---|
| .. | ||
| gnome-shell-sass | ||
| calendar-arrow-left.svg | ||
| calendar-arrow-right.svg | ||
| calendar-today.svg | ||
| checkbox-focused.svg | ||
| checkbox-off-focused.svg | ||
| checkbox-off.svg | ||
| checkbox.svg | ||
| close-window-active.svg | ||
| close-window-hover.svg | ||
| close-window.svg | ||
| close.svg | ||
| corner-ripple-ltr.png | ||
| corner-ripple-rtl.png | ||
| dash-placeholder.svg | ||
| filter-selected-ltr.svg | ||
| filter-selected-rtl.svg | ||
| gnome-shell-high-contrast.scss | ||
| gnome-shell.scss | ||
| key-enter.svg | ||
| key-hide.svg | ||
| key-layout.svg | ||
| key-shift-latched-uppercase.svg | ||
| key-shift-uppercase.svg | ||
| key-shift.svg | ||
| logged-in-indicator.svg | ||
| meson.build | ||
| message-indicator-symbolic.svg | ||
| no-events.svg | ||
| no-notifications.svg | ||
| noise-texture.png | ||
| pad-osd.css | ||
| page-indicator-active.svg | ||
| page-indicator-checked.svg | ||
| page-indicator-hover.svg | ||
| page-indicator-inactive.svg | ||
| process-working.svg | ||
| README.md | ||
| running-indicator.svg | ||
| source-button-border.svg | ||
| summary-counter.svg | ||
| toggle-off-hc.svg | ||
| toggle-off-intl.svg | ||
| toggle-off-us.svg | ||
| toggle-on-hc.svg | ||
| toggle-on-intl.svg | ||
| toggle-on-us.svg | ||
| ws-switch-arrow-down.png | ||
| ws-switch-arrow-up.png | ||
Summary
Do not edit the CSS directly, edit the source SCSS files and the CSS files will be generated automatically when building with meson + ninja and left inside the build directory to be incorporated into the gresource XML (you'll need to have sassc installed).
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:
| File | Description |
|---|---|
| _colors.scss | global color definitions. We keep the number of defined colors to a necessary minimum, most colors are derived from a handful of basics. It is an exact copy of the gtk+ counterpart. Light theme is used for the classic theme and dark is for GNOME3 shell default. |
| _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 on its web page. Once you make your changes to the _common.scss file, you can run ninja to generate the final CSS files.