Mercurial > pidgin.yaz
view libpurple/dbus-define-api.h @ 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 | 32c366eeeb99 |
children |
line wrap: on
line source
#error "This is file is not a valid C code" /* This file contains some of the macros from other header files as function declarations. This does not make sense in C, but it provides type information for the dbus-analyze-functions.py program, which makes these macros callable by DBUS. */ /* blist.h */ gboolean PURPLE_BLIST_NODE_IS_CHAT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_BUDDY(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_CONTACT(PurpleBlistNode *node); gboolean PURPLE_BLIST_NODE_IS_GROUP(PurpleBlistNode *node); gboolean PURPLE_BUDDY_IS_ONLINE(PurpleBuddy *buddy); gboolean PURPLE_BLIST_NODE_HAS_FLAG(PurpleBlistNode *node, int flags); gboolean PURPLE_BLIST_NODE_SHOULD_SAVE(PurpleBlistNode *node); /* connection.h */ gboolean PURPLE_CONNECTION_IS_CONNECTED(PurpleConnection *connection); gboolean PURPLE_CONNECTION_IS_VALID(PurpleConnection *connection); /* conversation.h */ PurpleConvIm *PURPLE_CONV_IM(const PurpleConversation *conversation); PurpleConvIm *PURPLE_CONV_CHAT(const PurpleConversation *conversation);