Mercurial > pidgin
view libpurple/purple-client-example.c @ 17574:f2869d5facfe
Fix #318 which asked for the buddynote plugins notes to be shown in the
tooltip. This was the easiest way I could think of to do it without making the
buddynote plugin itself a gtk plugin. Eventually I think I'll see about moving
the drawing-tooltip function to be a core plugin and this can get merged into
buddynote itself. (But I don't think that can't happen until 3.0.0.)
author | Etan Reisner <pidgin@unreliablesource.net> |
---|---|
date | Sun, 10 Jun 2007 07:25:09 +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; }