view libpurple/purple-client-example.c @ 17576:d495103dcf88

Two questions: 1. XMPP <status> messages inside <presence> broadcasts should be plaintext and not HTML, right? 2. 'stripped = purple_markup_strip_html(str)' is basically the same as 'purple_markup_html_to_xhtml(str, NULL, &stripped)', right? This fixes a bug Emily found where setting an XMPP status message with an embedded link would drop the link completely. For example, in Pidgin you set your away message and insert a link so that the message body is <a href="http://www.example.com/">Example</a>. When we set this message for an XMPP account it just strips the HTML and sets the message to "Example". This change causes the message to be "Example (http://www.example.com/)". It's the same thing we do when displaying links in tooltips in the blist.

#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;
}