view doc/ui-ops.dox @ 31204:f1874b08b3f9

Add unit tests for oscar_util_name_compare. I suspected that this function missed a few cases, but I was wrong, it's good. I used ck_assert_int_eq and ck_assert_ne, which look like they might be newer API. If that causes a problem we can change them to fail_if and fail_unless
author Mark Doliner <mark@kingant.net>
date Mon, 14 Feb 2011 03:10:09 +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