[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: a desktop wide "presence state" handling
From: "Christopher Blauvelt" <cblauvelt () gmail ! com>
Date: 2006-12-20 22:47:21
Message-ID: ffa898c90612201447i7becdc9fx85a3ab7630d12e95 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Why couldn't it merely be a "state change" signal with a bitmask as a
parameter telling you the status (away, busy, available, playing football,
whatever)? It seems like this would be the easiest to work with. This
would also work with statuses that don't make sense to some applications,
like "invisible" which is only applicable to IM clients, in that you could
have multiple presence statuses (invisible and away).
Chris
On 12/20/06, Anarky <anarky@ifrance.com> wrote:
>
> First, thanks a lot for your answer.
>
> John Tapsell wrote:
> > The way I see it though is there should just be 2 dbus signals in
> > kdestop (or something) which emit signals for when the user is away,
> > and when they are back.
>
> Didn't even know there was already something to see if the user is away or
> not
> in KDE itself.
> Do you know where it's used (screensaver, ...) ?
>
> As I see it, your suggestion is a first step, but I'd like to go beyond.
>
> Actually, every app that is interested in the presence of the user handle
> it
> with its own code because just knowing that the user is here or not isn't
> enough in most of the case.
> Kopete, for example, has a lot of states between "away" and "here".
> I'd like to make it possible for them to use a centralized place.
>
> An interesting use case would be to auto set me as "occupied" when
> watching a
> movie.
> This can't be done with just 2 dbus signals I think.
>
> Julien
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>
[Attachment #5 (text/html)]
Why couldn't it merely be a "state change" signal with a bitmask as a \
parameter telling you the status (away, busy, available, playing football, \
whatever)? It seems like this would be the easiest to work with. This \
would also work with statuses that don't make sense to some applications, like \
"invisible" which is only applicable to IM clients, in that you could have \
multiple presence statuses (invisible and away). <br>Chris<br><br><div><span \
class="gmail_quote">On 12/20/06, <b class="gmail_sendername">Anarky</b> <<a \
href="mailto:anarky@ifrance.com">anarky@ifrance.com</a>> wrote:</span><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> First, thanks a lot for your answer.<br><br>John \
Tapsell wrote:<br>> The way I see it though is there should just be 2 \
dbus signals in<br>> kdestop (or something) which emit signals for when the user \
is away,<br>> and when they are back. <br><br>Didn't even know there was \
already something to see if the user is away or not<br>in KDE itself.<br>Do you know \
where it's used (screensaver, ...) ?<br><br>As I see it, your suggestion is a \
first step, but I'd like to go beyond. <br><br>Actually, every app that is \
interested in the presence of the user handle it<br>with its own code because just \
knowing that the user is here or not isn't<br>enough in most of the \
case.<br>Kopete, for example, has a lot of states between "away" and \
"here". <br>I'd like to make it possible for them to use a centralized \
place.<br><br>An interesting use case would be to auto set me as "occupied" \
when watching a<br>movie.<br>This can't be done with just 2 dbus signals I think. \
<br><br>Julien<br><br>>> Visit <a \
href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> \
to unsubscribe <<<br></blockquote></div><br>
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic