Didn't have much time to code today, had to visit some family. Had a good meal ;-)
I hacked some DBUS support into XScreensaver today. Xscreensaver *should* send out a signal on the session bus now when the screensaver starts, or when it stops. Now guess what: it doesn't work (for now). Some security thing which disables me from sending events on my session bus :-(
Patch is here.
When this works, I will write a plugin for Gaim, which listens to the session bus. If it catches a screensaver event, it'll set your status to "Away" when the screensaver is started, and make you "Available" when the screensaver is stopped, if you were so when it started.
I created a new subdomain, http://code.eikke.com, where coding stuff will be hosted. I'd need some fancy "index" script, because Apache indexing doesn't work :-( I'd also need a decent Subversion repository. Maybe I should ask the guys who are so kind to host me (you know who you are).
Got some other new DBUS-based idea too, I'll discuss it on the dbus and gnome-desktop mailing lists when I get time.
Sent the mail to the dbus list regarding the kernel events stuff. Now it looks like I wasn't subscribed on that list anymore, and I need moderation... Hope they'll read and allow it soon.
Comments:
2 comments:
1. your subdomain is "forbidden" now
2. a hint for your gaim-plugin: maybe you could save the status of the accounts when the screensaver starts and restore them after the screensaver stops? Would be better so because if you were "busy" before screensaver, you don't want to be "available" then ;-)
You can do what you want by using something analagous to xscreensaver-command -watch.
1. Is normal, need to add some "site"
2. Thats what I meant in my text. But you know, my english...