kwin/org.kde.KWin.Plugins.xml
Vlad Zahorodnii c766e5da6d Introduce infrastructure for compositor extensions
The scripting api is not suitable for implementing all features that
should not be implemented in libkwin. For example, the krunner
integration or screencasting are the things that don't belong to be
compiled right into kwin and yet we don't have any other choice.

This change introduces a quick and dirty plugin infrastructure that
can be used to implement things such as colord integration, krunner
integration, etc.
2020-11-24 15:50:33 +00:00

32 lines
1 KiB
XML

<!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN" "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
<node>
<interface name="org.kde.KWin.Plugins">
<!--
The list of all currently loaded plugins.
-->
<property name="LoadedPlugins" type="as" access="read"/>
<!--
The list of all available plugins.
-->
<property name="AvailablePlugins" type="as" access="read"/>
<!--
Loads a plugin with the specified @a name.
If the plugin has been loaded successfully, @c true will be returned;
otherwise @c false is returned.
-->
<method name="LoadPlugin">
<arg type="b" direction="out"/>
<arg name="name" type="s" direction="in"/>
</method>
<!--
Unloads a plugin with the specified @a name.
-->
<method name="UnloadPlugin">
<arg name="name" type="s" direction="in"/>
</method>
</interface>
</node>