| Tue, 15 Jul 2008 17:21:17 +0000 |
Evan Schoenberg |
Allow macros in the plugin name when compiling statically.
|
| Sat, 10 Nov 2007 04:52:20 +0000 |
Ka-Hing Cheung |
propagate from branch 'im.pidgin.pidgin.next.minor' (head 0c9637482b845cc65e95a26e144697391c51133f)
|
| Wed, 10 Oct 2007 03:57:39 +0000 |
Richard Laager |
propagate from branch 'im.pidgin.pidgin' (head 1e697229b1c9a564fa1e509cc9a4a83da6e664df)
|
| Sun, 07 Oct 2007 16:02:55 +0000 |
Richard Laager |
* Add purple_plugin_disable() to prevent plugins from loading on the next
|
| Sun, 07 Oct 2007 14:58:23 +0000 |
Richard Laager |
I think we're doing the proper checks now, so remove a TODO. If this is
|
| Sat, 06 Oct 2007 22:59:09 +0000 |
Richard Laager |
Honor a PURPLE_DISABLE_DEPRECATED define to allow plugins to catch
|
| Sat, 06 Oct 2007 22:47:38 +0000 |
Richard Laager |
Deprecate the purple_plugins_register_* and purple_plugins_unregister_* functions. We have plugin-load and plugin-unload signals.
|
| Wed, 17 Oct 2007 03:36:54 +0000 |
Etan Reisner |
Replace a bunch of @return markers with @constreturn markers. I believe these
|
| Sat, 06 Oct 2007 18:08:21 +0000 |
Will Thompson |
All the links to libpurple signal pages were in the comment containing the
|
| Sun, 16 Sep 2007 01:05:22 +0000 |
Sean Egan |
remove gpl boilerplate from doxygen docs
|
| Mon, 10 Sep 2007 13:57:15 +0000 |
Daniel Atallah |
merge of '1c7910841138381c841363256ca3c7905b1f26b0'
|
| Sat, 08 Sep 2007 03:09:35 +0000 |
John Bailey |
The FSF changed its address a while ago; our files were out of date.
|
| Wed, 11 Jul 2007 22:27:44 +0000 |
Andreas Monitzer |
propagate from branch 'im.pidgin.pidgin' (head b195e262642015df66e36d33e9dd16ecae5df9d5)
|
| Fri, 29 Jun 2007 15:30:22 +0000 |
Sadrul Habib Chowdhury |
Add links to the signal documents in the API documents.
|
| Mon, 25 Jun 2007 19:08:16 +0000 |
Andreas Monitzer |
The server's ad-hoc commands are now listed in the account's action menu. Note that this requires an additional field in the _PurplePluginAction struct. There's no other way, since there was no way to supply user_data, and dynamically created functions are not supported by C. This should be fine, since that struct is only malloced in purple_plugin_action_new, which is part of the core. Applications have to either pass the struct unmodified, or restore the user_data pointer if the action is recreated when necessary (as is the case in Adium).
|
