doc/ui-ops.dox@b62ae35b71ed
doc/ui-ops.dox
Tue, 21 Jul 2009 23:45:49 +0000
- author
- Etan Reisner <deryni@pidgin.im>
- date
- Tue, 21 Jul 2009 23:45:49 +0000
- changeset 27927
- b62ae35b71ed
- parent 22526
- 4223bc1ce147
- child 34958
- 102488cc3c05
- permissions
- -rw-r--r--
merge of '8a058554f86508b8aff7b45367184ff0b4cd3adc'
and 'f0bc9d8b23450915a67513356ecd0c56eb185fd4'
/** @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
