[ekiga] Made an opal account explicitly an Ekiga::PresencePublisher and Ekiga::PresenceFetcher

[Julien Puydt <jpuydt src gnome org>]

commit 313ccb0ba9bdcf8d4650bd675cdc3231d2d2a1d6
Author: Snark <jpuydt gnome org>
Date:   Sun Dec 26 21:52:00 2010 +0100

    Made an opal account explicitly an Ekiga::PresencePublisher and Ekiga::PresenceFetcher
    
    That changes two things :
    (1) looks cleaner ;
    (2) we gain the right signals which will allow pushing the received presence
    and status information up the stack.

 lib/engine/components/opal/opal-account.h |   10 +++++++---
 1 files changed, 7 insertions(+), 3 deletions(-)
---
diff --git a/lib/engine/components/opal/opal-account.h b/lib/engine/components/opal/opal-account.h
index 24f75f2..6e3e179 100644
--- a/lib/engine/components/opal/opal-account.h
+++ b/lib/engine/components/opal/opal-account.h
@@ -41,6 +41,7 @@
 #include <opal/pres_ent.h>
 
 #include "services.h"
+#include "presence-core.h"
 #include "account-core.h"
 #include "personal-details.h"
 #include "account.h"
@@ -54,7 +55,10 @@ namespace Opal
    * @internal
    * @{
    */
-  class Account: public Ekiga::Account
+  class Account:
+    public Ekiga::Account,
+    public Ekiga::PresencePublisher,
+    public Ekiga::PresenceFetcher
   {
 public:
 
@@ -146,8 +150,8 @@ public:
     boost::signal0<void> trigger_saving;
 
     /*
-     * This part of the api allows using each account to handle
-     * some piece of the presence
+     * This is because an opal account is an Ekiga::PresencePublisher
+     * and an Ekiga::PresenceFetcher
      */
     void publish (const Ekiga::PersonalDetails& details);
     void fetch (const std::string uri);