view doc/ui-ops.dox @ 22891:43233dc1d40b

applied changes from 4c5110037671f84e3e775214c32692b5b23c11e1 through ae37fe6b64c30704715a369df88bd76674a39b1a applied changes from 4c5110037671f84e3e775214c32692b5b23c11e1 through ae37fe6b64c30704715a369df88bd76674a39b1a applied changes from b28057d6ade7c221b0616c3b02e86659e2d8b10b through 52c0efb045580dac7b6f5e40c91002e917e0cae3 Plucked changes for the chat-join-failed signal and associated server.c function from im.pidgin.pidgin, as these necessitate a minor version bump.
author Evan Schoenberg <evan.s@dreskin.net>
date Tue, 29 Apr 2008 03:59:28 +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