view doc/ui-ops.dox @ 20151:48374dc14adc

merge of '05931acee44dc92b25bb11c8d65ccf224d7f0ea8' and '1c2aa9589d0454ffcbf69e05a63cd3da005b3c2c'
author Daniel Atallah <daniel.atallah@gmail.com>
date Tue, 18 Sep 2007 03:10:40 +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