[SFLphone] python CLI client

[Juan M. Sanchez]

Sorry, forgot to copy to the list.

----- Forwarded message from "Juan M. Sanchez" <juanmasg at arrakis.es> -----

From: "Juan M. Sanchez" <juanmasg at arrakis.es>
To: Emmanuel Milou <emmanuel.milou at savoirfairelinux.com>
Subject: Re: python CLI client

On Wed, May 06, 2009 at 05:27:09PM -0400, Emmanuel Milou wrote:
> Juan M. Sanchez a écrit :
>> Hello Manu,
>>
>> Not having the daemon call list accesible from the client is being a 
>> problem. Too much work to implement a feature that will not be needed 
>> when you implement the method to access the call list via
>> dbus.
>>
>> The script is almost finished (I'm now only doing code cleanups and
>> optimizations), but it will not be complete as a softphone until I can 
>> get the real list of calls.
>>
>>   
> This feature is planned for the 0.9.6 version, I will do it as soon as  
> possible. The related ticket is  
> http://projects.savoirfairelinux.net/issues/show/1312
> You may update it with your request. I will implement a DBUS method so  
> that the client could retrieve the list of the call ID's from the  
> daemon. Will it be enough for you?
That will be great. This feature is needed for the client to be
completely syncronized with the daemon and with other clients.
I think that it will be needed to be able to get the call state also,
maybe in getCallDetails. I'll update the ticket to include this request.

The CLI client is completely not interactive for now, it is just a layer
over dbus for easier management from command line, accepting options
instead of those horrible d-bus calls needed by dbus-send.

It is designed this way, because the target for this application is to
be used as helper for integrating a softphone in AwesomeWM, and I just
needed to send commands and receive events from sflphoned.

In the future, it should be upgraded (or forked) for it to be able to
accept commands from readline, or using a curses interface.

>
>> As for now, it is able to execute all account and call actions
>> from command line arguments, and it has a "daemon" mode, where it prints
>> to stdout the events received from incomingCall and callStateChanged.
>>
>> Tell me if you want me to send you this initial version for running your
>> tests against the daemon.
>>   
>
> Yes of course I would like to test it !  Great job by the way, thank you  
> for your contribution.
No please, thank you for this software. I've been looking for a
replacement for SJPhone for a while. I wanted it to be completely usable
using keybindings. After trying out sflphone it has been really easy :-D

By the way, I'm a system administrator not a software developer, so, please 
forgive me if the coding is not the best. Let me know if you see 
something that should be changed, and I'll change it.

As I said, it is now almost completed (apart from some code
optimizations and cleanups), but when it be able to obtain the
call list and its status, it will be able to avoid too many potential
sflphoned crashes due to invalid arguments sent to some methods (reject
a call that is not rejectable, getCallDetails from a call that doesn't
exist, etc).

It's finally based on your work. It was better designed than what I had
:P.
Just type ./sflphonectrlsimple.py --help to get the list of options.

Cheers,


-- 
Juanma Sanchez
-

-------------- next part --------------
A non-text attachment was scrubbed...
Name: pysflphone.tgz
Type: application/x-gtar
Size: 5714 bytes
Desc: not available
Url : http://lists.savoirfairelinux.net/pipermail/sflphone/attachments/20090507/e329f42d/attachment.tgz