view doc/ui-ops.dox @ 27994:2ee64cfbbe2e

Check in a change that does dumb client-side blocking of people on your block list, for when the protocol doesn't do it for us. I think this is the behavior user's expect, and most of us seemed to be in favor of this when we talked about it on the devel list recently. This is really just to hold us over until Sulabh's privay changes are ready.
author Mark Doliner <mark@kingant.net>
date Tue, 18 Aug 2009 22:31:39 +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