QDBusInterface is useful for runtime introspection but little else.
As we know the interface in advance we can generate the keyboard layouts
interface and have non blocking, easier to read, easier to maintain
code.
broulik |
Plasma |
QDBusInterface is useful for runtime introspection but little else.
As we know the interface in advance we can generate the keyboard layouts
interface and have non blocking, easier to read, easier to maintain
code.
Opened lock screen, it had the whole list, cycled between them
Automatic diff as part of commit; lint not applicable. |
Automatic diff as part of commit; unit tests not applicable. |
Does it mean we now have to manually synchronize DBus API here in .xml and on KWin side?
Only if the API breaks (which is pretty much guaranteed not to happen) or we need a need field / function from the DBUS API.
Does it mean we now have to manually synchronize DBus API here in .xml and on KWin side?
It does, but that's easier to do that keeping code in sync
I wonder if we could "share" that .xml between server and client somehow..
We do in some cases. Interface headers are installed into /usr/share/dbus-1/interfaces
Then KWinDBusInterfaceConfig.cmake.in tells other projects where these files are