view doc/ui-ops.dox @ 20342:d4cdca890d8e

applied changes from 4d9fac4aab275ee133ce860edc469e0e5c4734ff through 68d63cab97f8861a7a080c3103d5e24a31587473 applied changes from 68d63cab97f8861a7a080c3103d5e24a31587473 through f9d3abd0678a04291edd671c4e5d87c7217984bb
author Luke Schierer <lschiere@pidgin.im>
date Sun, 21 Oct 2007 04:39:02 +0000
parents 500c785c109d
children e3bf822c19c8
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
   - #PurpleIdleUiOps
   - #PurpleNotifyUiOps
   - #PurplePrivacyUiOps
   - #PurpleRequestUiOps
   - #PurpleRoomlistUiOps
   - #PurpleSoundUiOps
   - #PurpleWhiteboardUiOps
   - #PurpleXferUiOps

 */
// vim: ft=c.doxygen