I decided to challenge myself to write a chat bot for Jami. I wanted to use the DBus API so I’m not forced to use Python. However I can’t seem to successfully build the API document. On Linux
I’ve ran the following commands in my attempt at building it. However I still don’t see a Makefile being generated.
cd extras/tools
./bootstrap
make
cd ../..
cd contrib
mkdir native
cd native
../bootstrap
make -j
cd ../..
./autogen.sh
./configure
wow, this directory is old and should not exists. The .xml are in bin/dbus. Actually, generally the best thing is to get d-feet, all api are visible, will remove this directory next week
Interesting. I presume that you mean that the .xml files are in /usr/share/dbus-1/interfaces
I would very much like to develop an interface for jami on linux phones, for example the pinephone. I can confirm that jami runs well on linux phones. but the interface is almost impossible to use. We need an interface similar to the android one.
Since there is no working cli I assume that I must try using dbus, but, without any documentation, this will be hard.
I would very much like to develop an interface for jami on linux phones
In my opinion, jami-qt should be responsive and should be usable. I use it on my pinephone. This will avoid to do a client from scratch, and it already have a lot of things. Tweaking the interface will be less painful in my opinion and can have a great value
I have not yet been able to get jami-qt to run on my arch linux pinephone.
The error is fairly simple, but I do not know how to solve it yet:
$ jami-qt
qt.qpa.plugin: Could not find the Qt platform plugin “wayland” in “”
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
and:
Got keys from plugin meta data QList(“xcb”)
QFactoryLoader::QFactoryLoader() checking directory path “/usr/bin/platforms” …
Absolutely, it is not necessary to reinvent the wheel, but perhaps a simple Call/Chat front ned which can open the jami client for detailed settings might be one approach.
Unfortunately the media settings are not fine grained enough. I think the the only way (at present) to select “Internal Earpiece” instead of “Internal Speaker” is though pulseaudio. What I was looking for is a button that can switch between earpiece and speaker during a call.