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.

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

Separate specto from the configuration gui #55

Open
GoogleCodeExporter opened this issue Aug 19, 2015 · 3 comments
Open

Separate specto from the configuration gui #55

GoogleCodeExporter opened this issue Aug 19, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

This is kind of huge, I know, but specto really should be separated in
preferences (which would contain both the actual preferences the watch
list) and the daemon, as right now the only way to change the preferences
and add, remove or deactivate watches while specto is running is to run it
with it always being in the notification area, which just isn't as cool.
btw, keep up the good work, I'm replacing mail-notification with spectro.

Original issue reported on code.google.com by [email protected] on 21 Apr 2007 at 10:08

@GoogleCodeExporter
Copy link
Author

Hey, guess what.  Your wish is our next major refactoring :).  Just don't expect
anything really soon.

Original comment by [email protected] on 23 Apr 2007 at 4:23

@GoogleCodeExporter
Copy link
Author

Original comment by [email protected] on 23 Apr 2007 at 4:24

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

Hello,

I started to play with d-bus so then we will have a specto daemon and a specto 
user 
interface.

I created a test daemon and a listener, but i think my code is not really 
clean, so 
any help would be appreciated!

Original comment by [email protected] on 29 Jan 2009 at 7:33

  • Changed state: Started
  • Added labels: Milestone-Release0.4

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