Changes between Version 4 and Version 5 of WhatIsLibpurple

Timestamp:

Apr 26, 2007, 4:57:14 AM (17 years ago)

Author:

MarkDoliner

Comment:

--

WhatIsLibpurple

@@ -3 +3 @@
 libpurple is intended to be the core of an IM program.  When using libpurple, you'll basically be writing a UI for this core chunk of code.  Pidgin is a GTK+ frontend to libpurple, Finch is an ncurses frontend, and Adium is a Cocoa frontend.
 
-Your program provides the int main() function.  Your main function will call libpurple_core_init(), which initializes libpurple.  Your main function will also register a whole bunch of "callback" functions that are called by libpurple any time there is something to tell the user.  For example, when libpurple receives an IM it'll call your function for handling an incoming IM.  When one of your buddies signs online libpurple will call your function to update the buddylist.
+= How does it work? =
 
-If your user fetches someones info then you'll call a libpurple function that sends the appropriate message across the network.  Then libpurple will get a response and call your function for handling buddy info.
+You write a program in C or C++ that provides all the fancy windows and dialogs and anything that the user interacts with.  Your program registers a bunch of callback functions, called "UI ops," with libpurple.  This is done by populating the appropriate uiops structures (eg. PurpleAccountUiOps, PurpleBlistUiOps, etc.) and making them available to the libpurple core (by calling purple_account_set_ui_ops, purple_blist_set_ui_ops, etc.).  Thes ui ops are triggered  at specific events.  For example, the buddylist ui ops are used to update your buddylist window when a new buddy is added, or if a buddy goes away, or becomes idle, etc.
 
-=== TODO: Combine the following text with the above ===
-
-Applications that use libgaim provide the appropriate functions to perform the UI operations invoked by the core (libgaim). This is done by populating the uiops structures (eg. GaimAccountUiOps, GaimBlistUiOps etc.) and making them available to the core (by calling gaim_accounts_set_ui_ops, gaim_blist_set_ui_ops etc.). The functions in the uiops are triggered at specific events, eg. the buddylist-uiops are used to update the buddy list when a new buddy is added, or removed, or the status of a buddy is changed etc. The same happens for conversations, logging etc.
+Your program provides the int main() function.  Your main function will call libpurple_core_init() which initializes libpurple.  Your main function will also register a whole bunch of "callback" functions that are called by libpurple any time there is something to tell the user.  For example, when libpurple receives an IM it'll call your function for handling an incoming IM.  When one of your buddies signs online then libpurple will call your function to update the buddylist.  The same thing happens for conversations, logging etc.
 
 While the uiops are sufficient for most of the ui operations, it's likely that you will want to use the gaim-signals as well to fine-tune some stuff.
+
+If your user fetches someone's info then you'll call a libpurple function that sends the appropriate message across the network.  Then libpurple will get a response and call your function for handling buddy info.
 
 libgaim uses the glib mainloop to do all the things. The application wanting to use libgaim will [likely] have to do the same.