ObjFW  View Ticket

2024-06-01
13:22 Ticket [1fd9b87257] Add D-Bus implementation status still Open with 3 other changes artifact: 973e5940fe user: js
2024-05-22
20:13 Ticket [1fd9b87257]: 1 change artifact: 2e2b386439 user: js
00:12 Ticket [1fd9b87257]: 3 changes artifact: fe0a04adc0 user: js
2024-01-27
20:11 Ticket [1fd9b87257]: 4 changes artifact: f2ac0428df user: letterus
10:41 New ticket [1fd9b87257]. artifact: 4244185dda user: js

Ticket UUID: 1fd9b87257ad22cd6ab86d993f7bc243f85f0b68
Title: Add D-Bus implementation
Status: Open Type: Feature Request
Severity: Minor Priority: Low
Subsystem: Resolution: Open
Last Modified: 2024-06-01 13:22:24
Version Found In: Milestone:
User Comments:
js added on 2024-01-27 10:41:06:

D-Bus is used for more and more things. It probably makes sense to add a D-Bus implementation.


letterus added on 2024-01-27 20:11:27:

Maybe it's interesting to have a native implementation. But keep in mind ObjGTK will generate wrappers for GLib's GIO library which has an high level API for DBus. So it could be worth to watch out for improving that one.

Unreleased ObjGTK GIO Wrappers, OGDBus* classes.


js added on 2024-06-01 13:22:24:

Given more and more things on Linux require D-Bus these days (e.g. in order to discover the path of a device, as that is handled by systemd these days), a D-Bus implementation should probably be part of ObjFW itself and not limited to GTK applications using ObjFW.