[Konversation-devel] Global "away state" gestion

[Julien Bigot]

Hi,

I'm crossposting this e-mail because I'd like to know you're feelings about a 
feature that would like to implement in KDE

that feature is a global gestion of away state in KDE ( 
http://bugs.kde.org/show_bug.cgi?id=129020 )

Basicaly the idea is that a global "away state" is set for kde (including 
the "not away" state).
This set is hold by a state daemon.
This daemon is configured in the kde config center to auto change "away 
states" according to certain trigger events.
Then, messages are sent (through dbus ?) to all application when state changes 
so that application can react as they want to each "away state".
Of course it should also be possible to ask the daemon to know what is the 
current state.

I think that to begin, I'll develop a version with a few different fixed 
states (let's say jabber states for example) and with a message.
But in the future, I'd like to allow the user to define it's own states and to 
program the reaction of each application to this state.

For example :
when I'm in state "sleeping", set kopete & konvesation away with away 
message "sleeping", set kde notifications to "no sound" and stop Amarok.

I think a good thing could be to propose application groups (a bit like in 
phonon) to allow to set ll IM applications away, to shut down all mm apps, 
etc ...

The main question is : do you think it's a good idea ? Would you like to 
implement support for all that in your respective applications ?

Let me know if you have suggestions.

regards,

Julien Bigot