Skip to content

Latest commit

 

History

History
160 lines (127 loc) · 4.88 KB

Worklog.org

File metadata and controls

160 lines (127 loc) · 4.88 KB
Raw

Distribution

Hackage

Uploading Package to Hackage

cabal check
stack sdist

# Upload as package candidate: https://hackage.haskell.org/packages/candidates/upload

# Upload
# Change version in path:
cabal upload .stack-work/dist/x86_64-linux-tinfo6/Cabal-2.2.0.1/deadd-notification-center-1.7.3.tar.gz

Issues

Sizes configurable (CLOSED)

  • [X] Window dimensions for all windows

Buttons with info-updates (CLOSED)

  • [X] Problem: i don’t know if multiple hints per noti are possible… yes they are

Buttons at bottom (CLOSED)

  • In the configuration one could specify button-captions and shell-commands
  • The buttons could be generated dynamically
  • [X] Problem: all commands are executed simultaneously… solved
  • [X] Problem 2: to many buttons overlap to the right

More styling (#2, CLOSED)

Color configurable (CLOSED)

  • [X] done

Multiple Screen support (#1)

Aur does not build (#4)

Notifications stuck (#5, CLOSED)

  1. fixed race condition
  2. created new bug (replaceid does not work anymore)
  3. Easy fix (a + 1 to much)…

Transient Notifications (#6, CLOSED)

  • ignoreTransient configuration added

If you want to send transient notifications (notifications that should not be stored in the notification center, but only showed once) yourself, you can do so with notify-send:

notify-send --hint=int:transient:1 "My Caption" "My Body..."

Sort notis by time with newest on top (CLOSED)

Notification based scripting (#3, #6, CLOSED)

Fixing build issue (CLOSED)

Handling of XML tags (CLOSED)

Signals (NotificationClosed) (CLOSED)

  • Implemented but disabled by default
    • WHY?: Because e.g. Spotify takes the NotificationClosed message as a reason to not replace old notifications but to send a new one. As the Notifications are stored in the center after being closed though, they would accumulate.
    • If you want the NotificationClosed message for some reason anyways, you can script the NotificationClosed message for certain notifications away by using the noClosedMsg option. For more information on this, consult Notification based scripting (#3, #6, CLOSED).
    • To enable the NotificationClosed message, set configSendNotiClosedDbusMessage to true in the notification-center section of your config file.
    • Why is the default for configSendNotiClosedDbusMessage false? Because, for a new user it is not obvious, that e.g. Spotify does what it does how it does it and might be highly extremely annoyed by that behaviour without knowing, it could be prevented. The need for that NotificationClosed is not very apparent to me anyways.
    • What a wast of time to implement this stupid NotificationClosed, jeeeze.

Actions (CLOSED)

Image support

Bin-Package

  • No build time
  • No compilation issues

Translation of program