view doc/ui-ops.dox @ 21496:0df3d6b11d05

merge of '29c59c7fc04cdf75b2debfab42171f298f82c5fc' and 'd5c59d95a2f6dee5e7af2653c48c880594d8528a'
author Will Thompson <will.thompson@collabora.co.uk>
date Wed, 14 Nov 2007 12:16:30 +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