Mercurial > pidgin
view libpurple/purple-send-async @ 18913:1d243e70db35
Refactor msim_tooltip_text() and msim_get_info_cb(), so that they now both use
one function, msim_append_user_info(), to create PurpleNotifyUserInfo. The
information now always comes from an MsimUser instead of sometimes coming from
MsimUser (for tooltip text) and sometimes from a user info protocol reply,
msim_store_buddy_info() now can store user information from an MsimMessage
into any MsimUser (such as a temporary user created when doing get info on
someone not on your buddy list), or into the MsimUser of PurpleBuddy.proto_data.
author | Jeffrey Connelly <jaconnel@calpoly.edu> |
---|---|
date | Mon, 13 Aug 2007 00:38:43 +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