view libpurple/purple-client-example.c @ 16741:a2e9890a57e0

Implement msim_pack(), msim_sendh(), msim_send(). msim_pack() converts a hash table to a protocol message string. msim_sendh() sends a protocol message using msim_send_raw, after converting the hash table to a string using msim_pack(). msim_send() accepts variable arguments and converts them to a hash table, then sends using msim_sendh(). These are part of the TODO item "Generic protocol message sending function, that handles packing of messages", but functions haven't been updated to use msim_send() instead of msim_send_raw() yet.
author Jeffrey Connelly <jaconnel@calpoly.edu>
date Sun, 20 May 2007 07:08:57 +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;
}