doc/ui-ops.dox@cdd4b0dfe92b
doc/ui-ops.dox
Sun, 28 Apr 2013 11:13:24 +0200
- author
- Tomasz Wasilczyk <tomkiewicz@cpw.pidgin.im>
- date
- Sun, 28 Apr 2013 11:13:24 +0200
- branch
- soc.2008.masterpassword
- changeset 34165
- cdd4b0dfe92b
- parent 22526
- 4223bc1ce147
- child 34958
- 102488cc3c05
- permissions
- -rw-r--r--
keyring.c refactoring: use signal instead of hack depending on implementation
/** @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
