view doc/ui-ops.dox @ 25562:2a34a3f5da2e

applied changes from 20269e8849976ad6a0996f79ccbc0a12a311484f through e9af692071731a2eec5087a51005e19b74012e93 applied changes from e1b1e80d999e393a80f201a484ef61289c258fbe through 20269e8849976ad6a0996f79ccbc0a12a311484f applied changes from e9af692071731a2eec5087a51005e19b74012e93 through e0170b7d1bb1bb03c7354d57d2d249842528f163 Add libpurple version info to pidgin --version, /debug, and About.
author Ethan Blanton <elb@pidgin.im>
date Tue, 28 Apr 2009 20:14:08 +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