Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improved notification server #2

Open
4 of 10 tasks
erikinkinen opened this issue Feb 17, 2024 · 0 comments
Open
4 of 10 tasks

Improved notification server #2

erikinkinen opened this issue Feb 17, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@erikinkinen
Copy link
Member

This issue is to track features to be implemented in the notification server.

  • "persistent" capability
  • Summary
  • "body" capability
  • CloseNotification method
  • NotificationClosed signal (NB. This is critical because it is required by the spec.)
  • "sound" capability (NB. Although we play sound, we need to support the "sound-file" and "suppress-sound" hints to be XDG compliant.)
  • ActionInvoked signal (NB. This partially ovelaps with the "actions" capability. This signal can however be used without the cap to invoke the notification itself (and not a specific action). XDG spec states this is optional.)
  • "actions" capability
  • "icon-static" capability
  • ActivationToken signal (NB. cutie-wlc needs to support xdg-activation-v1 for this.)

I personally believe the other capabilities defined by the spec are not desired in our use case. If you think otherwise, please leave a comment.
@erikinkinen erikinkinen added the enhancement New feature or request label Feb 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
The Board
Status: In Progress
Milestone
No milestone
Development

No branches or pull requests
1 participant
@erikinkinen