Damien Sandras a écrit :
What about the API proposal you have in mind ?
(a basic draft about the various classes that will be involved is
enough).
I had in mind something very very basic for the elementary chunks :
std::liststd::string get_info (const std::string key) const;
(and of course
Le lundi 19 octobre 2009 à 17:06 +0200, Julien Puydt a écrit :
Hi,
here are some thoughts on the merged contact+presentity system we want
in ekiga 4.
The main idea is the following : with the current code, you choose a
contact in the evolution addressbook and copy some of it over to
Hi,
here are some thoughts on the merged contact+presentity system we want
in ekiga 4.
The main idea is the following : with the current code, you choose a
contact in the evolution addressbook and copy some of it over to the
roster. This works pretty well, but has a few consequences : what
Julien Puydt wrote:
Hi,
here are some thoughts on the merged contact+presentity system we want
in ekiga 4.
The main idea is the following : with the current code, you choose a
contact in the evolution addressbook and copy some of it over to the
roster. This works pretty well, but has a
Eugen Dedu a écrit :
Julien Puydt wrote:
Hi,
here are some thoughts on the merged contact+presentity system we want
in ekiga 4.
The main idea is the following : with the current code, you choose a
contact in the evolution addressbook and copy some of it over to the
roster. This works pretty
