Ship a notification daemon

[goodboy]

Been debating whether to include something as part of the base daemon set and I'm starting to think that's the right way to go. This pertains mostly to the landing of #140 for which most testers had trouble groking the notify daemon setup.

Expecting (newb) users to modify their system setup with a notification daemon is likely a losing battle and it probably can't hurt to include a recommendation for a specific daemon (ex. dunst) and we can include a default config that's used in the case nothing is already on the d-bus.

Ideally we get these features:

• spawned as part of pikerd, fails gracefully if bus is already in use
• notification is customized to be same style as existing piker pallette (ish)
  • doable with dunst using the cmdline config options
• a click on the notification triggers a focus on the notifying program
  • dunst has actions which allows for indicators and embedded urls

  • The "context" keybinding is used to interact with these actions, by showing a menu of possible actions. This feature requires "dmenu" or a dmenu drop-in replacement present.

• we'll likely want an integration with i3ipc-python, for eg here's an embedded app searcher
  • figuring out how to call this from the notifyd will be interesting, though maybe not so bad if we spawn dunst in a known env?
• keep mako and #139 in mind

More to come!

[goodboy]

Oh we probably want to think about how all this can interplay with a Qt tray icon eventually too!

[goodboy]

Tips on how to get notifications on windows using win10toast.

Not that this has any priority.