Bug 263008 - Suggestion on usage of DBus names
Summary: Suggestion on usage of DBus names
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: 4.6
Platform: Compiled Sources All
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-13 10:24 UTC by Artem Anisimov
Modified: 2020-10-29 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Artem Anisimov 2011-01-13 10:24:51 UTC
Version:           4.6 (using KDE 4.5.95) 
OS:                All

I have filed bug #263006 where I complained that kwordquiz lost its ability to switch keyboard layout on the fly after DBus methods of KXKB have been renamed.

Decision to rename methods of exported kdelibs API that can be used by external programs is already a not-so-good idea. What was even worse is that kwordquiz had these names hardcoded and I had to make the same modification to 4 unrelated source files.

Such error would have never happened if DBus interface names had been registered in a single well-known place. I suggest that kdelibs have a well-known header file (say, kdelibs-dbus-interfaces.h) that lists names of every interface that KDE (or at least, its core components) exports to DBus.

Making such interfaces registry will not avoid surprises to external applications if you ever decide to rename your methods but at least programs that make up KDE SC will have coherent idea of how DBus is to be used.


Reproducible: Always
Comment 1 Nate Graham 2020-09-29 22:21:21 UTC
Is this still a problem or a reasonable request?
Comment 2 Bug Janitor Service 2020-10-14 04:33:24 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2020-10-29 04:33:42 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!