Hi, while using some of the scripts already available for BE::Shell i realized that maybe (as the title said) a script should do the job: i think that a way to control ktp it's needed. I thought it can be done through QDbus. Any tip?
E.g. Commands to change the status?
Commands to check the status ( i think there should be a Haze log somewere for checking msn)?
Last edit: Hombremaledicto 2012-11-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you, that's already something, i've just obtained a good thing to start with. =)
Really you've never heard about telepathy? O.O
Anyway, if it's not a problem i'd like to keep this discussion open, if there are others than me are interested in.
EDIT: org.kde.ktp-contactlist
The issue comes with the fact that ktelepathy should be AFAIK a client for telepathy protocol, and it's structured in different packages(each one restricted to different jobs).
Last edit: Hombremaledicto 2012-11-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok - it seems that for manage accounts and their status it uses mc-tool ( at least, that's what i discover from telepathy-mission-control package). I'm going to check what "man mc-tool" explains about it....
Hi, while using some of the scripts already available for BE::Shell i realized that maybe (as the title said) a script should do the job: i think that a way to control ktp it's needed. I thought it can be done through QDbus. Any tip?
E.g. Commands to change the status?
Commands to check the status ( i think there should be a Haze log somewere for checking msn)?
Last edit: Hombremaledicto 2012-11-05
probably - but i don't even know what that is (seems some IM framework -> nothing i care about at all, i hate synchronous communication ;-)
i'd start by running "qdbus | grep telepat" while whatever that is, is running ;-)
Thank you, that's already something, i've just obtained a good thing to start with. =)
Really you've never heard about telepathy? O.O
Anyway, if it's not a problem i'd like to keep this discussion open, if there are others than me are interested in.
EDIT: org.kde.ktp-contactlist
The issue comes with the fact that ktelepathy should be AFAIK a client for telepathy protocol, and it's structured in different packages(each one restricted to different jobs).
Last edit: Hombremaledicto 2012-11-05
Nope. Show me screenshot that explains what it is and why i need it =)
If i however understood it correctly, you should be able to contact whatever it is w/o actually a graphical client running.
Yeah, that's the point! =D
I think that it should work without any GUI.
Here's the shot: http://ompldr.org/vZzVxNQ
BTW there are other packages like ktp-logger, ktp-haze (for msn etc...), handler(i think for file-transfer) etc....
Ok - it seems that for manage accounts and their status it uses mc-tool ( at least, that's what i discover from telepathy-mission-control package). I'm going to check what "man mc-tool" explains about it....
EDIT: TO Check the name of your account:
"mc-tool list"
to go online:
"mc-tool request ACCOUNT online
So here's a primal example of menu: http://pastebin.com/KVph0xXk
Last edit: Hombremaledicto 2012-11-06
Ok here's a more complete menu: http://pastebin.com/kQ9k4Yj0
Where in MYACCOUNT you have to enter the account name given by mc-tool list command.
To keep the connection opened after closing the contact list:
nano ~/.kde4/share/config/ktp-contactlistrc
and change the string:
go_offline_when_closing=true
to false. Save and log in again.
Now the only thing that it's needed is a status update script to change the icon for the button according to the account's one =)
Last edit: Hombremaledicto 2012-11-06