Bug 327555

Summary:	add stable dbus api
Product:	[Applications] kdeconnect	Reporter:	maxim.suraev
Component:	common	Assignee:	Albert Vaca Cintora <albertvaka>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	arthur
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description maxim.suraev 2013-11-13 11:26:17 UTC

Right now kdeconnect provides 2 set of dbus api:
/module/kdeconnect which governs adding/removing devices and multiple
/modules/kdeconnect/devices/123456 where 123456 is phone-specific id which is unpredictable
This renders automated code generation tools based on dbus introspection unusable.
Would be great to have stable dbus api available under /modules/kdeconnect/devices with the same methods (sendPing(), isPaired(), charge() etc) but with one additional parameter indicating device id: "String id".
This would greatly simplify using kdeconnect dbus api.

Reproducible: Always

Comment 1 Albert Vaca Cintora 2019-01-07 17:52:46 UTC

It's not a bad idea, but we are not going to do BOTH approaches and we won't break backwards compatibility for this.

Scripting becomes a bit more convoluted the way it is, but it is still possible since you can discover all subpaths withing a path in dbus.