Most of this post is fairly old news, but still worth to be mentioned.
Also as a small gimmick (and because it was requested in my previous post), here is a gif of the new slide-out animation of xfce4-notifyd 0.4.0
I have read your comments and bugreports and have already been working towards some further improvements of notifyd, so I guess 0.4.1 is around the corner.
Finally, here goes the “historic news”.
After a longer waiting time I pushed out another development release of the panel. This one includes among as major change the port to GDBus, which was done by Ali. This means the panel now depends on xfconf 4.13 – recommended is at least 4.13.3 – and is not compatible anymore with xfconf 4.12.
A lot of bugfixes and translation updates accumulated over the last months since 4.13.0, the most prominent one is the fix of drag and drop (one of the bigger known regressions of the Gtk+3 port) thanks to Peter. A nice new improvement is the re-ordering of systray items, which was implemented by Viktor.
We’ve had a lot of problems with keyboard shortcuts not working reliably with the panel plugin and systray version of clipman so Mike rolled up his sleeves and ported both to GtkApplication. I haven’t had a problem with my keyboard shortcuts since!
This release features some small improvements including slimmer CSD/headerbars to save some vertical pixels, initial support for Xfdesktop 4.13 to help all testers of Xfce’s development releases and finally a fix for message dialog buttons.
I have since then been working towards supporting Thunar’s Gtk+3 port better in Greybird, which will be included in the next release.
After quite some development time I have decided to push out xfce4-notifyd 0.4.0 today. This is not just a bugfix, but a feature-packed release.
Among the biggest changes there is a panel plugin which displays the most recent notifications as well as allowing for quick access to the do-not-disturb mode. It also serves as a status indicator for the do-not-disturb mode, so you can easily see whether notifications are shown or hidden overall.
I’ve also spent some time on improving the notification image handling in the log. While handling icon-names is easy (just save them as string) handling the pixbufs was a little more challenging. I decided to do it the Git way and deduplicate these pixbufs based on their (unique) hashes, so that each picture would only be saved once. All of those pictures end up in a sub-directory of the log (which by default is ~/.cache/xfce4/notifyd/icons). Currently there is no monitoring of how much space these images consume and no button to clear them away, maybe I’ll add that later if people feel it would be useful/necessary. After using this feature for several months I have accumulated less than 7MB.
The log also received some more love in terms of markup support and character escaping. Multi-line notifications should now be correctly logged.
New animation: slide-out
Just for the fun of it I also worked out a new animation optional addon to the standard fade-out. I called it slide-out and it’s a fairly wide-spread animation mix of fade-out and sliding the bubble (depending on its location on the screen of course) off-screen.
As this turned out to be a bigger release I went for a bigger version jump and also included the new logo I had been working on for a while. I evaluated several “notification” metaphors and went for the ‘ol bell (notification bubbles felt a little odd and not easy to depict, as they look usually very diverse).
Some people may be happy to know that I dropped the feature that let xfce4-notifyd exit after 10 minutes of inactivity. I can only guess but I presume this was implemented to save resources. Nowadays it feels more annoying if a daemon has to be restarted and the first notification that’s that split-second longer to appear.
A few more tweaks have been done to the geometry of the notification bubble windows to not take more space than needed and distribute things evenly (no more strange margins) and the configuration dialog now shows a warning if xfce4-notifyd is not detected as running.
As always, you can download and build/install the tarball or wait for your favorite distribution to package and ship it to you.