You can try to add DBus in Kate (application) rather than KTextEditor (framework).

In D10587#207857, @anthonyfieroni wrote:

You can try to add DBus in Kate (application) rather than KTextEditor (framework).

Won't that break compatibility? (and fail to cover KWrite or other similar applications?)

It will not break compatibility or you should supposed how? Kate and KWrite present in same repo, so the code can be shared, but yes it will not have this feature in other apps that uses KTextEditor. But you can read @cullmann wrote in bug report that it doesn't want KTextEditor to depend on QDBus.

In D10587#207874, @anthonyfieroni wrote:

It will not break compatibility or you should supposed how? Kate and KWrite present in same repo, so the code can be shared, but yes it will not have this feature in other apps that uses KTextEditor. But you can read @cullmann wrote in bug report that it doesn't want KTextEditor to depend on QDBus.

I don't think I would know how to make these changes. I was only able to get this to work because it was mostly a simple revert.

This change has history, for reference: https://git.reviewboard.kde.org/r/129398/

In D10587#207885, @lukedashjr wrote:

I don't think I would know how to make these changes. I was only able to get this to work because it was mostly a simple revert.

It should be same: at https://phabricator.kde.org/source/kate/browse/master/kate/katedocmanager.cpp;2641fc835e5fecb539122dcfbee1caa42617ebe4$89

qRegisterMetaType<KTextEditor::Document*>("KTextEditor::Document*");
new DocumentAdaptor(doc);
const QString pathName = QString::fromLatin1("/Kate/Document/%1").arg(++dbusDocumentNumber);
QDBusConnection::sessionBus().registerObject(pathName, doc, QDBusConnection::ExportAdaptors | QDBusConnection::ExportScriptableSlots);

And all others. You can test it or adapt it?