Does Dolphin have a Dbus API and if so then where might the documentation be?

For instance, I would like to automate being able to change the sftp file path in a Dolphin window from a shell script or RMB action.

You can usually browse the Dbus api for an app by using something like qdbus (command-line app) or qdbusviewer (gui).
Doing a quick browse, I didn't see anything useful (mostly just interacting with the gui itself).

An alternative idea is to just use xdg-open with the uri and (so long as the association is set up properly) it should open up in dolphin automatically (though I'd assume in a new window rather than an existing window).

Thanks for clarifying @airdrik. I should do battle with qdbusviewer and see if there is any hint of something useful to interact with Dolphin from a shell script...

OMG, qdbusviewer is in the qt4-dev-tools deb package which pulls in a swag of Qt4 dev packages! Pass. Sigh.

Oh how I miss the old Amiga days, 30 years ago, which had https://en.wikipedia.org/wiki/ARexx

In my wildest dreams I could imagine some combination of LUA and DBus could mostly emulate what AREXX enabled and as an avid Amiga user back in the day I can vouch for how utterly amazing and useful that functionality was and find it hard to believe it remains unimplemented in the 21st century.

markc wrote:
OMG, qdbusviewer is in the qt4-dev-tools deb package which pulls in a swag of Qt4 dev packages! Pass. Sigh.

Debian packages - qdbusviewer: https://packages.debian.org/search?sear ... e&arch=any

=> Qt5 package is qttools5-dev-tools

Hmm, my kubuntu artful system must be messed up then...

Code: Select all

~ dpkg -L qttools5-dev-tools | grep dbus
/usr/lib/x86_64-linux-gnu/qt5/bin/qdbusviewer
~ qdbusviewer
qdbusviewer: could not exec '/usr/lib/x86_64-linux-gnu/qt4/bin/qdbusviewer': No such file or directory


Oh, is this something to do with not having set qtchooser (or whatever it is)?

I don't know for sure, but you could just create your own application entry.
Browse to ~/.local/share/applications and create a new Link to Application. Make sure to use the full path to the executable in the Command field on the Application tab.
The .desktop links in ~/.local/share/applications should show up in most menus/launchers.