view doc/ui-ops.dox @ 20148:e86f136e880e

merge of 'abe5c21ff8b83812c256bc2b14a3f887ecc628b8' and 'bf8de57ed4c36f188044ea0684c201d0a1a67169'
author Jeffrey Connelly <jaconnel@calpoly.edu>
date Tue, 18 Sep 2007 01:08:46 +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