Mercurial > pidgin.yaz
view doc/ui-ops.dox @ 20346:07c2e60026da
applied changes from e9e74094baa29c6f5589385507221a2502b817fb
through 9c0eac6528c65b06c0ac062dd0f682bf594522cb
applied changes from ca09db83bd2ae802d4a6d7078a1efdfe9a896cb5
through 55c9e6a9c4728a7d3394eb9f5c6042bc0657e72d
applied changes from 7d6d68e181cad51516162cb1ccf769a1204c4688
through 99cf68a5d3604fa8f1e05918e5b370a6a4991cd1
applied changes from 99cf68a5d3604fa8f1e05918e5b370a6a4991cd1
through 111659964eabcb60dd83e3598df42b5d4b788a90
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Sun, 21 Oct 2007 04:44:56 +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