+++ /dev/null
-Pidgin-autoanswer, v. 0.71
-
-This plugin for Pidgin performs itself like an answering machine or, more likely, a prompter robot. It tries to find suitable answers in your previous logs with current buddy and prompts its variants. Robot's AI is extremely poor, but the theory of probability works wonders sometimes. :) Or, at least, you will get your portion of fun :))
-List of configurable features includes mode of answering without your permission (off by default), as far as robot's prefix to answers (for example if you want it to preface each answer with something like "The best answer is") and maximum amount of variants (to prevent the plugin from becoming a resource hog).
-
-Requirements:
-
-The pidgin header files are needed to compile the plugin.
-
-Building & installation:
-
-To build and install :
- You can compile the plugin using
- $ make
- and install it with
- $ make install
- This will install it in ~/.purple/plugins so that only the user who install it can use it.
-
-To install it for everybody on your computer,
- $ make
- $ su
- # make install PREFIX="/path/to/pidgin" (this command as root user)
- generally /path/to/pidgin is /usr or /usr/local. If you don't know the path then you can find out using
- $ whereis pidgin
- and look for the part before "/lib/pidgin".
-
-Using the plugin:
-
-Being enabled in pidgin preferences, plugin is activated each time when new message comes. If there are some analogs in logs, robot adds a combobox with previous times answers to the conversation panel (and possibly lists variants in the conversation, if allowed in preferences). To use proposed answer one should choose it in combobox and confirm the choice by pressing "Say" button on the left.
-
-Find new version:
-
-Please check http://sourceforge.net/projects/pidgin-autoansw for updates, if any.
-
-Contributions:
-
-Developed by Dmitriy Kostiuk (d.k@list.ru)
-Early prototype was partially coded by Timothy Tupchik and Andrey Smirnov. Some code is still there (mainly one for scanning logs).
-Also much regards for strstr() function which for now acts as robot's IQ :)
-
-
+++ /dev/null
-TODO:
- * process everything asynchronously
clean:
rm -rf *.o *.c~ *.h~ *.so *.la .libs
+
+user:
+ cp -r purple/* $(HOME)/.purple/
--- /dev/null
+libPurple core-answerscripts plugin
+
+This simple plugin just passes every single message received by any libPurple-based client (pidgin,finch) to sript(s) in user's home directory... So you can add various hooks to your pidgin or finch without need of writing and compiling own C plugin or messing with buggy perl plugin and restarting client after each change in plugin.
+
+There are already few sample (answer)scripts in purple directory, so you can check how easy it is to write some script for pidgin or finch...
+
+
+The libpurple header files are needed to compile the plugin.
+
+Building & installation:
+
+To build and install :
+ You can compile the plugin using
+ $ make
+ and install it with
+ $ make install
+ This will install it in ~/.purple/plugins so that only the user who install it can use it.
+ $ make user
+ Install main script and sample answerscripts to ~/.purple/answerscripts.d/
+
+To install it for everybody on your computer,
+ $ make
+ $ su
+ # make install PREFIX="/path/to/pidgin" (this command as root user)
+ generally /path/to/pidgin is /usr or /usr/local. If you don't know the path then you can find out using
+ $ whereis pidgin
+ and look for the part before "/lib/pidgin".
--- /dev/null
+TODO:
+ * right now pidgin shows response before request (just on our side of course :-)
+ * process everything asynchronously
+ * general speed improvement
+ * more example scripts (user contributions welcome)
"Framework for writing various hooks for libpurple clients",
"This plugin will call ~/.purple/" HOOK_SCRIPT " (or wherever purple_user_dir() points) "
"script (or any executable) for each single message called."
- "Envinronment values PURPLE_FROM and PURPLE_FROM will be set to carry "
+ "Envinronment values PURPLE_MSG and PURPLE_FROM will be set to carry "
"informations about message text and sender so script can respond to that message. "
"Any text printed to STDOUT by the script will be sent back as answer to message. "
"Please see example scripts for more informations...",