Mercurial > pidgin.yaz
view PLUGIN_HOWTO @ 15144:b81e4e44b509
[gaim-migrate @ 17929]
User Info and Tooltips now use the GaimNotifyUserInfo object and methods defined in notify.h. GaimNotifyUserInfo objects encapsulate a list of GaimNotifyUserInfoEntry objects, each of which may have a label, a value, and be specified to be a section header.
This moves the burden of UI generation of user information from the various prpls to the UI. The UI can choose how to display the information rather than being fenced into a particular HTML formatting. Consistency across the prpls' information presentation is now enforced, as well. gaim_notify_user_info_get_text_with_newline() generates text in the:
<b>label</b>: value
<b>label</b>: value
format as was passed by convention from prpls in the past.
committer: Tailor Script <tailor@pidgin.im>
author | Evan Schoenberg <evan.s@dreskin.net> |
---|---|
date | Sun, 10 Dec 2006 02:53:09 +0000 |
parents | 7acebc9d043f |
children | cc3c50816cc9 |
line wrap: on
line source
For information on writing a plugin for Gaim, go http://gaim.sourceforge.net/api/ and see the HOWTOs in the "Related Pages" section. You can also generate this documentation locally by installing doxygen and graphviz dot, then running "make docs" in the Gaim source tree. The documentation will be in the docs/html directory. This next paragraph is old and possibly out of date: Compilation of the plugins is fairly straight-forward; there is a Makefile in this directory that has a rule for making the .so file from a .c file. No modification of the Makefile should be necessary, unless if you simply want to type 'make' to have it made; otherwise, 'make filename.so' will take filename.c and make the .so plugin from it. If you need to link in with extra libraries, you can set the environment variable PLUGIN_LIBS to be the libraries you want to link with. It should be possible to compile plugins outside of the Gaim source tree, which is a much cleaner solution.