Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 20550:28493a27849b
Looking at purple_contact_set_alias and purple_blist_alias_contact functions
in blist.c, the only difference I see is that the latter function
notifies any existing conversation with the contact so that it can update
its title, while the former doesn't. I can't think of a reason why they
should behave differently, or why we should have both of them. I was going
to deprecate purple_blist_alias_contact in favour of purple_contact_set_alias,
but seeing we do purple_blist_alias_ for buddy and chats, I am deprecating
purple_contact_set_alias instead. OK?
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Wed, 19 Sep 2007 10:01:45 +0000 |
parents | c6e563dfaa7a |
children | 48d09d62912e |
line wrap: on
line source
#define DBUS_API_SUBJECT_TO_CHANGE #include <stdio.h> #include <stdlib.h> #include "purple-client.h" /* This example demonstrates how to use libpurple-client to communicate with purple. The names and signatures of functions provided by libpurple-client are the same as those in purple. However, all structures (such as PurpleAccount) are opaque, that is, you can only use pointer to them. In fact, these pointers DO NOT actually point to anything, they are just integer identifiers of assigned to these structures by purple. So NEVER try to dereference these pointers. Integer ids as disguised as pointers to provide type checking and prevent mistakes such as passing an id of PurpleAccount when an id of PurpleBuddy is expected. According to glib manual, this technique is portable. */ int main (int argc, char **argv) { GList *alist, *node; purple_init(); alist = purple_accounts_get_all(); for (node = alist; node != NULL; node = node->next) { PurpleAccount *account = (PurpleAccount*) node->data; char *name = purple_account_get_username(account); g_print("Name: %s\n", name); g_free(name); } g_list_free(alist); return 0; }