view doc/ui-ops.dox @ 23627:a270bd4b5298

Just a few little cleanups. * I think we try to pair g_strdup() with g_free(). I don't know if it actually matters, but theoretically it could. * Changed this to use g_slist_prepend() when adding stuff to the queue. * Changed purple_requesticqstatusnote() to check if the linked list is empty and return TRUE as soon as the list becomes empty rather than on the next call to that function. * Don't remove and re-add the timer if it's already set. Unless there was a reason for that?
author Mark Doliner <mark@kingant.net>
date Mon, 21 Jul 2008 07:46:23 +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