view doc/ui-ops.dox @ 30289:ca60dd3812fa

applied changes from 8b6590428d8180cc466c8916f81aec2c8961fbd1 through 1f5f812e500972cfb805d2cf0b3bc423cf2b7f3f This hack to manually handle X-GOOGLE-TOKEN an X-FACEBOOK-PLATFORM shouldn't be needed now; avoiding them was masking the problem, since we should be prepared for a server to offer any number of arbitrary mechs which we may or may not be able to handle.
author Evan Schoenberg <evan.s@dreskin.net>
date Tue, 04 May 2010 02:10:02 +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