view libpurple/purple-send @ 22933:d464485a2bfc

Clean up the comments about MSNP14, and make the --enable-msnp14 option no longer commented out. This makes it possible, with stock pidgin, to build with msnp14 using --enable-msnp14 - are we ready for this? (my thought being that if we are ready for this we can see what happens when "early adopters" turn it on and maybe, just maybe, making msnp14 default for 2.5.0)

#!/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