Re: [Ekiga-devel-list] Blacklisting
- From: Julien Puydt <jpuydt free fr>
- To: Ekiga development mailing list <ekiga-devel-list gnome org>
- Subject: Re: [Ekiga-devel-list] Blacklisting
- Date: Mon, 22 Jan 2007 10:08:35 +0100
Jan Schampera a écrit :
On Sun, 24 Dec 2006 10:46:03 +0100
Julien Puydt <jpuydt free fr> wrote:
I have thought about this.
May I try to summarize (correct me if I'm wrong)
Introduce a call-activity handler that
(1) Is controlled directly or indirectly by the endpoint
(2) fires signals as notification of call state changes (similar to DBUS
external behaviour)
(3) processes a list of call-state handlers in order of some abstract
priority and react on their return code
(4) don't mix up the meaning of the handlers for (2) and (3) ;-)
Hmmm... the idea is to have an endpoint GObject, which is controlled
very directly by the endpoint C++ object, and fires signals for various
things.
There would be a main call-handler GObject, which would watch the
endpoint GObject for call informations. All other call-handlers would
register to the main one.
Is it clearer?
Snark
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]