view libpurple/purple-send @ 22776:01e375e9b681

disapproval of revision '8086f2cffaab6ed17431381836b9227a64a53270' This really needs to happen with the appropriate magic necessary to allow adding newer functions when necessary without forcing a bump in the major. I am not necessarily succumbing to 'fear of incrementing a version number' or anything, I just don't think this particular feature is important or useful enough. I would be interested to see if there's still any confusion left after the change from 'Screenname' to 'Username'.

#!/bin/sh

METHOD_NAME=$1

if test -z "$METHOD_NAME" 
then
    cat <<EOF 
This program calls purple API functions using DBus and prints the return value.
If you are not interested in the return value, use purple-send-async.

Usage:

   $0 method-name type1:parameter1 type2:parameter2 ...

This shell script just invokes dbus-send, see man dbus-send for how 
to specify the parameters.  

Examples:

   $0 PurpleAccountsFindConnected string: string:prpl-jabber
   $0 PurpleAccountsGetAll
   $0 PurpleCoreQuit

Use dbus-viewer to get the list of supported functions and their parameters.
EOF
    exit 1
fi

shift
dbus-send --dest=im.pidgin.purple.PurpleService --print-reply --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"

echo