Skip to content

Separate notifications daemon from shell client #123

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.

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

Closed
plfiorini opened this issue Jan 5, 2014 · 0 comments
Closed

Separate notifications daemon from shell client #123

plfiorini opened this issue Jan 5, 2014 · 0 comments

Comments

@plfiorini
Copy link
Member

Make notifications optional by moving the code to another process that can be launched using systemd.

@ghost ghost assigned plfiorini Jan 5, 2014
plfiorini added a commit that referenced this issue Jan 12, 2014
This way notifications can be managed more easily making Hawaii more
modular.

Issue: #123
plfiorini added a commit that referenced this issue Jan 12, 2014
No functional changes.

Issue: #123
plfiorini added a commit that referenced this issue Jan 12, 2014
Seems better for an executable.

Issue: #123
plfiorini added a commit that referenced this issue Jan 12, 2014
Listen to Wayland registry events and start the notifications daemon as
soon as wl_notification_daemon is registered.

Issue: #123
plfiorini added a commit that referenced this issue Jan 12, 2014
So that we can freely use it from NotificationWindow.

Issue: #123
@plfiorini plfiorini modified the milestones: Version 0.3.0, Version 0.2.1 Feb 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant