Mercurial > pidgin

view doc/ui-ops.dox @ 23366:98594354b423

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Don't cycle through a NULL "message" when purple_parse_oncoming() is called for an away oscar buddy. purple_got_infoblock() will supply a message as appropriate.
author Evan Schoenberg <evan.s@dreskin.net>
date Sat, 14 Jun 2008 19:12:47 +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