Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 30051:3b24193663bc
Change pidgin_convert_buddy_icon() to be more accommodating when attempting
to scale a large buddy icon. I spent entirely too much time on this, but
I'm pretty happy with the result.
We now try to set increasingly lower quality levels when trying to save
as a jpeg until we have an image that is smaller than the max file size
limit specified by the prpl. If the image is still too large when quality
level is 70, we'll try scaling down the image dimensions to be 80% of the
size we just tried.
Fixes #11565
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Sat, 27 Mar 2010 21:29:18 +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; }