| vkrause | |
| ogoffart | |
| mck182 |
| Plasma | |
| Frameworks |
This lets the application set an urgency hint on the notification, which can be low, normal, or critical.
The notification server can then apply different behavior, e.g. show critical notifications on top of full screen windows, or suppress low urgency notifications by default.
See https://developer.gnome.org/notification-spec/#urgency-levels
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
Nicely fits with the Android backend too, although that has one extra level (low, medium, high, urgent).
I found the following enums in NotificationManager:
I was looking at https://developer.android.com/training/notify-user/channels#importance which also has IMPORTANCE_LOW mapped to "medium". But yes, it's basically just about finding a suitable mapping, even if we don't cover every possible level on Android.
So, in essence you're fine with adding the enum as it is, and then have some mapping in the Android code? :)
@vkrause I just noticed xdg portal notification spec (the ones used for sandboxed flatpak apps) has four urgency levels: low, normal, *high*, critical.
Do you think it would be useful to add HighUrgency, too? For Android, maybe? For freedesktop Notifications we could just map High to Normal then (like Gnome does it).
It's not released yet, we can still meddle the enums for another few weeks :)
Yep, Urgent/High/Normal/Low would indeed match Android perfectly. Adding more enum values also should be possible later without breaking compatibility, unless we assume them to be in the right order anywhere. If we need them ordered, maybe explicitly assign them values to leave some space between them?