PINE64
Mobian libnotify custom notifications - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone Pro (https://forum.pine64.org/forumdisplay.php?fid=177)
+--- Forum: PinePhone Pro Software (https://forum.pine64.org/forumdisplay.php?fid=179)
+--- Thread: Mobian libnotify custom notifications (/showthread.php?tid=18557)



Mobian libnotify custom notifications - MadameMalady - 07-30-2023

I want my app to make use of custom made symbolic icons for notifications using libnotify; where should I put my icons? are svgs okay? wb a particular naming scheme?
Any help's appreciated!


RE: Mobian libnotify custom notifications - Kevin Kofler - 07-30-2023

/usr/share/icons/hicolor/scalable/status/ (for SVGs – for PNGs, use, e.g., 32x32 instead of scalable for a 32×32 PNG).


RE: Mobian libnotify custom notifications - MadameMalady - 07-30-2023

I put it there, this is how I'm trying to spawn the notification:

notify-send "My Waydroid Manager" "Done!" --icon=my-waydroid-manager-notify

the file is called my-waydroid-manager-notify.svg
I'm still getting a 'missing icon' icon in the notifications Sad


RE: Mobian libnotify custom notifications - MadameMalady - 07-31-2023

So, for anyone wondering, I figured it out, the proper way of doing this is:

notify-send -i /path/to/your/scalable/icon/example_notification_icon.svg "Name Of App" "This is the notifications body!"


RE: Mobian libnotify custom notifications - Kevin Kofler - 08-01-2023

If you install an icon to the systemwide hicolor theme, you need to run gtk-update-icon-cache for GTK to pick up the new icon. This is normally done in packages' post-installation scripts, see your distribution's (i.e., Mobian's in this case) packaging guidelines.

Using an absolute path to the icon works, but is not the recommended way to do things because it means the icon is not themable.


RE: Mobian libnotify custom notifications - MadameMalady - 08-01-2023

(08-01-2023, 07:27 AM)Kevin Kofler Wrote: If you install an icon to the systemwide hicolor theme, you need to run gtk-update-icon-cache for GTK to pick up the new icon. This is normally done in packages' post-installation scripts, see your distribution's (i.e., Mobian's in this case) packaging guidelines.

Using an absolute path to the icon works, but is not the recommended way to do things because it means the icon is not themable.

Good to know for the future, but in this case is the right move.
The icon is already designed to conform to the Gnome HIG, and doesn't need theming ootb.

(08-01-2023, 07:27 AM)Kevin Kofler Wrote: If you install an icon to the systemwide hicolor theme, you need to run gtk-update-icon-cache for GTK to pick up the new icon. This is normally done in packages' post-installation scripts, see your distribution's (i.e., Mobian's in this case) packaging guidelines.

Using an absolute path to the icon works, but is not the recommended way to do things because it means the icon is not themable.

The only official package I plan to support long-term as stated on the repo, are flatpaks,
volunteers are welcome to make pull requests for other distributions support, but I am one woman, and I'm gonna aim at what ik I can hit for now.
I'll worry abt more *officially supported* distributions if maintaining a flatpak turns out to be easy enough.
In general like many (most?) gtk4 / libadwaita app devs, I don't support theming ootb.
I plan to get light / dark theming taken care of for libadwaita and that is it.