doc/ui-ops.dox@4efd5d82fef3
doc/ui-ops.dox
Tue, 09 Feb 2010 22:40:36 +0000
- author
- Paul Aurich <darkrain42@pidgin.im>
- date
- Tue, 09 Feb 2010 22:40:36 +0000
- branch
- next.minor
- changeset 29694
- 4efd5d82fef3
- parent 22526
- 4223bc1ce147
- child 34958
- 102488cc3c05
- permissions
- -rw-r--r--
propagate from branch 'im.pidgin.pidgin' (head 413e8fd92b59bffd550111f0f0c60128eed53cd8)
to branch 'im.pidgin.pidgin.next.minor' (head 1f3d2781dc78bbc50ad34a729df1868c8028c6ce)
/** @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
