Re: [GnomeMeeting-devel-list] Refactoring the addressbook code
- From: Jose Carlos Garcia Sogo <jsogo debian org>
- To: gnomemeeting-devel-list gnome org
- Subject: Re: [GnomeMeeting-devel-list] Refactoring the addressbook code
- Date: Mon, 27 Mar 2006 23:46:38 +0200
El lun, 27-03-2006 a las 23:24 +0200, Damien Sandras escribió:
[...]
> > >
> > > In OPAL, you have C++ objects (backend). This C++ objects have methods,
> > > to take an action, and callbacks, which reacts to actions.
> >
> > You have the same in Gloox. When you connect to the server you will get
> > a roster in a RosterListener object that will handle roster callbacks.
> > This is clearly a backend, that perhaps can be mapped to a more generic
> > backend for dbus or other purposes.
> >
> > >
> > > In Ekiga, you have GTK+ functions (frontend). All functions defined by
> > > Jan are GTK+ functions. They do not manipulate the C++ objects, they
> > > only manipulate the GUI part of Ekiga.
> >
> > Yes, I see that, but I still think that we should define some general
> > backend functions that can be called by SIP/SIMPLE or Jabber endpoints,
> > and which call both gtk and dbus functions.
> >
>
> I agree with that, but Julien has another view (that I like, but don't
> think easily feasible enough).
Then, I don't have very clear yet how Julien thinks things should be
done. If he is interested in being able to map to dbus, he should agree
with that intermediate generic layer.
--
Jose Carlos Garcia Sogo
jsogo debian org
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]