[Gaim-patches] [ gaim-Patches-1153491 ] gaim-remote send and blist support

[SourceForge.net <no...@so...>]

Patches item #1153491, was opened at 2005-02-28 09:17
Message generated for change (Comment added) made by seanegan
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300235&aid=1153491&group_id=235

Category: Plugins
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Ayan Chakrabarti (ayanc)
Assigned to: Sean Egan (seanegan)
Summary: gaim-remote send and blist support

Initial Comment:
This patch adds support for blist and changes the send
behaviour in gaim-remote. Its based partly on the
suggestion Sean made on my earlier patch (which tried
to do everything in the URI code).

1. Blist - Allows retrieval of status of all buddies in
your buddy list, including whether they have a
conversation window open with you.

USAGE: gaim-remote blist filename

Each entry in filename will be in the format,

screenname:accountname:STATUS[:CONVERSING]

Status can be online/offline/disconnected (if that
particular gaim connnection is disconnected).

2. Send - This modifies the behaviour of gaim-remote
send from as is implemented now. If it is felt, that
the existing send behaviour is the required standard
behaviour, I could probably rename this to esend
(though this would require creating a new
CUI_REMOTE_ESEND thingie).

USAGE: gaim-remote send
screenname:account:message:historyfile

This sends message to screenname using account and if a
historyfile is specified, dumps the history of  that
particular conversation.

eg,
gaim-remote send ayan:irc:hey:/tmp/history

One can also choose to read the message from a file by
replacing message with %message,

gaim-remote send ayan:irc:%/tmp/asciiart:/tmp/history

In all these, the history file arguement may be left out,

gaim-remote send ayan:irc:hey

Also, the message arguement may be left blank, in which
case only the history will be retrieved,

gaim-remote send ayan:irc::/tmp/history

And finally, if both message and history are left out,
the plugin just closes the conversation window.

gaim-remote send ayan:irc::

The main reason I'm writing this is to able to control
gaim more or less completely from a console or from
scripts - including finding out who's online, who's
currently trying to talk to me and actually carrying
out conversations. 

----------------------------------------------------------------------

>Comment By: Sean Egan (seanegan)
Date: 2005-03-01 00:35

Message:
Logged In: YES 
user_id=199625

Every patch to gaim-remote I get is like this one. It uses
gaim-remote to pass the command-line input directly to Gaim
which parses it and spits back a single user-readable
string, which is then dumped to the screen as-is. 

Gaim-remote uses the CUI (core/ui split) protocol initially
designed (and ultimately destined) to allow for interfaces
to communicate with the Gaim core remotely. gaim-remote
happens to be an example of an interface that can do this,
but the core/ui protocol cannot be designed around gaim-remote.

I suppose it's because the only really useful part of
gaim-remote currently is gaim-remote uri, people get the
impression that this sort of thing is recommended. "parse
and execute this URI" just happens to be one function of the
cui protocol that takes exactly one string argument. What
you've done requires several arguments, an account, a
protocol, a recipient, a message, etc. You've essentially,
though, created your own "uri" format and renamed it "send"

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300235&aid=1153491&group_id=235