Trac is being migrated to new services! Issues can be found in our new
YouTrack instance and WIKI pages can be found on our
website.
- Timestamp:
-
Feb 8, 2007, 6:58:29 AM (17 years ago)
- Author:
-
MarkDoliner
- Comment:
-
Initial version
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v1
|
|
| 1 | libpurple is intended to be the core of an IM program. When using libpurple, |
| 2 | you'll basically be writing a UI for this core chunk of code. So Gaim is |
| 3 | really just a GTK+ frontend to libpurple, Gaim-text is an ncurses frontend, and |
| 4 | Adium is a Cocoa frontend. |
| 5 | |
| 6 | Your program provides the int main() function. Your main function will call |
| 7 | libpurple_core_init(), which initializes libpurple. Your main function will also |
| 8 | register a whole bunch of "callback" functions that are called by libpurple any |
| 9 | time there is something to tell the user. For example, when libpurple receives |
| 10 | an IM it'll call your function for handling an incoming IM. When one of your |
| 11 | buddies signs online libpurple will call your function to update the buddylist. |
| 12 | |
| 13 | If your user fetches someones info then you'll call a libpurple function that |
| 14 | sends the appropriate message across the network. Then libpurple will get a |
| 15 | response and call your function for handling buddy info. |
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!