view doc/ui-ops.dox @ 25432:256fbe98f6be

The jabber_register_parse function was looking for the <x> node as a child of the <iq> node instead of the <query> node. (See Chs 4 & 5 of XEP-0077) Somebody (maybe it'll be me?) should probably check that the code for these two cases does what it's supposed to, since I don't think it would have run before now. It also looks like the precedence may be wrong (See Ch 6).
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sat, 07 Feb 2009 23:45:18 +0000
parents e3bf822c19c8
children
line wrap: on
line source

/** @page ui-ops UiOps structures

  When implementing a UI for libpurple, you need to fill in various UiOps
  structures:

   - #PurpleAccountUiOps
   - #PurpleBlistUiOps
   - #PurpleConnectionUiOps
   - #PurpleConversationUiOps
   - #PurpleCoreUiOps
   - #PurpleDebugUiOps
   - #PurpleDnsQueryUiOps
   - #PurpleEventLoopUiOps (without this, nothing will work and you will cry)
   - #PurpleIdleUiOps
   - #PurpleNotifyUiOps
   - #PurplePrivacyUiOps
   - #PurpleRequestUiOps
   - #PurpleRoomlistUiOps
   - #PurpleSoundUiOps
   - #PurpleWhiteboardUiOps
   - #PurpleXferUiOps

 */
// vim: ft=c.doxygen