Mercurial > pidgin.yaz
view libpurple/purple-client-example.c @ 23959:8a488151e07a
Add 'Nested Grouping' option in the grouping plugin
Nested groups are detected by the '/' character in the group name. For
example, groups 'Work/Accounting' and 'Work/Lab' will both be nested
under a 'Work' parent group. It would probably make more sense to
actually name the subgroups 'Accounting' and 'Lab' in this case, and a
patch to make that happen will be gladly accepted.
I think some other client uses similar behaviour for group nestedness.
author | Sadrul Habib Chowdhury <imadil@gmail.com> |
---|---|
date | Sun, 31 Aug 2008 06:31:17 +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; }