view libpurple/purple-send-async @ 17703:0f4a562b38d1

libpurple should not use glib eventloop stuff directly, since we have our own eventloop abstraction. This leaves just one hack in blist.c.
author Richard Laager <rlaager@wiktel.com>
date Mon, 04 Jun 2007 04:50:02 +0000
parents 598b1b15b199
children 942bf314fc8a
line wrap: on
line source

#!/bin/bash

METHOD_NAME=$1

if test -z "$METHOD_NAME" 
then
    cat <<EOF 
This program calls purple API functions using DBus.  As opposed to purple-send, 
it does not print the return value.

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 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 --type=method_call /im/pidgin/purple/PurpleObject im.pidgin.purple.PurpleInterface.$METHOD_NAME "$@"

echo