Mercurial > pidgin.yaz
view PLUGIN_HOWTO @ 14875:7357d46ba817
[gaim-migrate @ 17644]
SF Patch #1586467 from Benjamin Moody - floppusmaximus
"Currently if a plugin creates a multi-line, non-HTML
string preference, i.e. a GaimPluginPref with type
GAIM_PLUGIN_PREF_STRING_FORMAT and format-type
GAIM_STRING_FORMAT_TYPE_MULTILINE, the resulting widget
is extremely narrow and impossible to use.
This is because the widget is packed into an hbox
without allowing expansion (expand = fill = FALSE.) If
HTML is enabled, the presence of the format bar forces
the widget to be wide enough to be usable. Disabling
HTML causes the format bar to be removed, so the widget
is set to the minimum allowed size."
committer: Tailor Script <tailor@pidgin.im>
author | Richard Laager <rlaager@wiktel.com> |
---|---|
date | Wed, 01 Nov 2006 02:13:37 +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.