bugaevc

tbernard, 11 days ago to random

Trying something for this app: https://flathub.org/apps/com.jeffser.Alpaca

Side note: the app works surprisingly well on my fairly old laptop, I'm kind of impressed.

zhuowei, 18 days ago to random

Taylor Swift, known for showing vulnerability in her lyrics, announces that each of her songs will receive its own CVE

bugaevc, 19 days ago to random

Remember to hydrate, fellow humans 💧

bugaevc, 23 days ago to random

nnethercote, 25 days ago to random

This video has 3 million views. It deserves more.

ENTIRE FREEBIRD SOLO PLAYED ON HARMONICA!!! (Lynyrd Skynyrd)

https://www.youtube.com/watch?v=UtXP2-5IC2E

brooke, 28 days ago to random

cat /dev/zero | gzip > strategic_zero_reserve.gz

alice, 30 days ago to random

So, CSS variable support has landed in GTK, and libadwaita now uses it. Note that it's super basic for now, it's just replacements for the old @colors. There will be more drastic changes in 2.0, but for now I need to keep backwards compatibility.

So, apps can now override them per widget, like on the screenshot (well, once the sdk updates, anyway)

And because why not, there are a few changes that variables enabled:

.error, .warning and .success style classes now also change the accent color respectively. For example, this means that a selectable label with .error style class will have a red selection as well, instead of blue.

The .opaque style class for buttons has been deprecated - instead, apps can simply use .suggested-action and override the accent color on it (or add .error/.warning/.success - that works too). This will also change the focus ring, and similarly, .destructive-action buttons have red focus rings now.

Apps are encouraged to migrate, but the old colors will keep working until 2.0. For example, @accent_color can be replaced with var(--accent-color) and so on, note the dashes in the names instead of underscores. See the docs for more info: https://gnome.pages.gitlab.gnome.org/libadwaita/doc/main/css-variables.html