Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 28155:1e02e65ce301
Changes to the way we translate raw yahoo messages to HTML. The HTML
is now well formed (we actually close tags now). The code isn't as
simple as I would like, but I'm happy with it. I think it's a pretty
robust solution and should still be pretty efficient. I didn't find
any memory leaks with valgrind.
The formatting used in yahoo messages is really ghetto.
Also added a lot more tests. They pass with and without the
USE_CSS_FORMATTING define.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Tue, 04 Aug 2009 02:14:46 +0000 |
parents | 48d09d62912e |
children |
line wrap: on
line source
#ifndef DBUS_API_SUBJECT_TO_CHANGE #define DBUS_API_SUBJECT_TO_CHANGE #endif #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; }