feat: add notification body message & text min-width (#7)

[d3cryptofc]

Done! It solves #7 issue. Review the PR please.

Added Features:

• Notification body message on a new line when present.

• Notification minimum width, consequently promoting symmetry and left alignment for text.

  I used an invisible character (\u205F) at the end of the spaces to prevent hyprland from trimming the spaces and making them disappear.

1. Without Body

2. With Body

The notification without an icon is subtly larger than the notifications that have an icon, unfortunately I didn't find better ways to compensate for the lack of an icon.

Important

Hyprland default font-family must be monospace on hyprland.conf misc section. See here: https://wiki.hyprland.org/Configuring/Variables/#misc

[Bloeckchengrafik]

nitpick: you could store this regex in a package-level variable to not recompile it every time this function is ran

[d3cryptofc]

You're right, I'll do it!

[d3cryptofc]

done! 024ba8b

[codelif]

Hey, Thanks for showing interest in "hyprnotify". Love the work you have done.

I wanted to add body to the text as well but never figured out a way it would fit well like this. So, I nuked it completely.

A nitpick:
Could you add "body" in the cap array in the GetServerCapabilities function?

https://specifications.freedesktop.org/notification-spec/latest/protocol.html#id-1.10.3.2.5

[codelif]

As for the font-family requirement, I don't think there is a way to change it just for the notification. Otherwise we could make it automatically change on startup through IPC.

Maybe a fallback mode could be implemented if font-family is not a monospace font.

[d3cryptofc]

A nitpick: Could you add "body" in the cap array in the GetServerCapabilities function?

https://specifications.freedesktop.org/notification-spec/latest/protocol.html#id-1.10.3.2.5
Supports body text. Some implementations may only show the summary (for instance, onscreen displays, marquee/scrollers)

This way?

func (n DBusNotify) GetCapabilities() ([]string, *dbus.Error) {
	cap := []string{"body"}
	return cap, nil
}

[codelif]

This way?

Yes!

[d3cryptofc]

Maybe a fallback mode could be implemented if font-family is not a monospace font.

Any idea for an alternative? The problem with non-monospaced fonts is that each character takes up different space in a text, the amount of padding could have to increase or decrease based on the character choices.

[codelif]

Maybe a fallback mode could be implemented if font-family is not a monospace font.

Any idea for an alternative? The problem with non-monospaced fonts is that each character takes up different space in a text, the amount of padding could have to increase or decrease based on the character choices.

I am creating an issue to track this, meanwhile I am merging this (though seems like a dead-end). Thanks for your contribution!