Mercurial > pidgin.yaz

annotate PLUGIN_HOWTO @ 32635:63e7d226b760

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Re-arrange these doxygen comments. For comments longer than a few words, putting the comment before the variable like this seems cleaner than trying to cram it on the same line as the variable and using lots of crazy indentation. Anyone have a strong opinion either way?
author Mark Doliner <mark@kingant.net>
date Sun, 18 Sep 2011 20:18:33 +0000
parents db5a58aabe38
children
Ignore whitespace changes - Everywhere: Within whitespace: At end of lines:
rev   line source
15937
cc3c50816cc9 More gaim->whatever isms
Mark Doliner <mark@kingant.net>
parents: 14505
diff changeset
1 For information on writing a plugin for Purple, Pidgin or Finch, go
28380
db5a58aabe38 Wrap this file more consistently.
Richard Laager <rlaager@wiktel.com>
parents: 16176
diff changeset
2 http://developer.pidgin.im and click on API. From there, see the
db5a58aabe38 Wrap this file more consistently.
Richard Laager <rlaager@wiktel.com>
parents: 16176
diff changeset
3 HOWTOs in the "Related Pages" section.
14505
7acebc9d043f [gaim-migrate @ 17225]
Mark Doliner <mark@kingant.net>
parents:
diff changeset
4
7acebc9d043f [gaim-migrate @ 17225]
Mark Doliner <mark@kingant.net>
parents:
diff changeset
5 You can also generate this documentation locally by installing
15937
cc3c50816cc9 More gaim->whatever isms
Mark Doliner <mark@kingant.net>
parents: 14505
diff changeset
6 doxygen and graphviz dot, then running "make docs" in the
14505
7acebc9d043f [gaim-migrate @ 17225]
Mark Doliner <mark@kingant.net>
parents:
diff changeset
7 source tree. The documentation will be in the docs/html directory.