Mercurial > pidgin
view libpurple/purple-client-example.c @ 19228:7131e5699991
Two changes here
1. In gtk_request_fields(), if there are enough fields to justify
the scrollbar, then add a 6 pixel padding around the inside of
the scrolled window so that the fields aren't crammed in there
like sardines. See /config in an XMPP chat, or Set User Info
for an XMPP account to see what it's like.
2. In the same place, if the dialog is resized larger then have
the widgets within the dialog expand to fill the extra space.
author | Mark Doliner <mark@kingant.net> |
---|---|
date | Mon, 13 Aug 2007 04:50:41 +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; }