view src/gaim-client-example.c @ 13131:47ecef83e2e1

[gaim-migrate @ 15493] A lot of our conversation code assumes that conv->account != NULL. This is a completely invalid assumption. If you have a conversation open on an account, and you delete the account, Gaim should leave the conversation window open and set the account to NULL and handle everything appropriately. Currently it does not, and that makes me a little unhappy. To reproduce this: 1. Open a conversation with someone 2. Delete the account that you're sending messages from 3. Watch the assertion failures scroll by in the debug window committer: Tailor Script <[e-mail]>

#define DBUS_API_SUBJECT_TO_CHANGE

#include <stdio.h>
#include <stdlib.h>

#include "gaim-client.h"

/* 
   This example demonstrates how to use libgaim-client to communicate
   with gaim.  The names and signatures of functions provided by
   libgaim-client are the same as those in gaim.  However, all
   structures (such as GaimAccount) 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 gaim.  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 GaimAccount when an id of
   GaimBuddy is expected.  According to glib manual, this technique is
   portable.
*/

int main (int argc, char **argv)
{
    GList *alist, *node;

    gaim_init();
    
    alist = gaim_accounts_get_all();
    for (node = alist; node; node = node->next) {
	GaimAccount *account = (GaimAccount*) node->data;
	char *name = gaim_account_get_username(account);
	g_print("Name: %s\n", name);
	g_free(name);
    }

    g_list_free(alist);

    return 0;
}