View Single Post
Posts: 356 | Thanked: 123 times | Joined on Dec 2008
#251
Originally Posted by uvatbc View Post
1. That dbus command does not open a chat room. You're confusing it with the contacts integration component that I introduced 2-3 months back. And yes, that button is broken. I'm not sure how I'm supposed to fix it yet, but I'll get to it.
The dbus API itself is working fine. I've tested it several times using my test utilities. You should be able to use it in QB.
2. That is something I've thought about for some time... It is kind of cumbersome right now to open qgvdial then click the dialpad and then click the switch button. It's not difficult to add the dbus api, it is difficult to make the api good enough that it will never need to change in the future. Also, the plumbing is difficult.

Besides, at this moment, I'm concentrating on mosquitto. I have been able to compile and run it on n810 and n900 and hopefully I'll be able to debianize and upload to extras devel soon (on both).
Once that is done, I'll be adding a mqtt subscriber in qgvdial that will wait for an "update now" message to refresh contacts, inbox or settings.
The publisher will be released for n810 and generic Linux - it will poll continuously for changes and post update messages to the server.
1. I was referring to the contacts integration component. I was just recommending that you make it open the window to send a text message instead of the chatroom window if that is possible (until you fix the chatroom).

2. I was actually referring to switching forwarding phones in a google voice account (which phones ring when your number is called).

I was just (today) looking into how to get mosquitto run on the n900 so I could try to setup a push service to the device. Let me know when you have a package ready.