view doc/ui-ops.dox @ 25371:be87547aa431

merge of '0bf6462dd433df38943094bbed0393698d91a037' and '9c4b346f6536ab35c06e2c6cabb905bae60c420d'
author Sadrul Habib Chowdhury <imadil@gmail.com>
date Sat, 13 Dec 2008 21:13:04 +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