21dbf0410f
We were using the plugin infrastructure to tell the name of the plugin
we were configuring.
Since this doesn't make any sense, just let the kcms themselves define
where they want their settings to be.
This fixes a regression from when we ported away from using KService to
list them.
|
||
---|---|---|
.. | ||
CMakeLists.txt | ||
kdeconnect_share.json | ||
kdeconnect_share_config.qml | ||
README | ||
share_config.cpp | ||
share_config.h | ||
share_config.ui | ||
shareplugin.cpp | ||
shareplugin.h |
It receives a packages with type kdeconnect.share. If they have a payload attached, it will download it as a file with the filename set in the field "filename" (string). If that field is not set it should generate a filename. If the content transferred is text, it can be sent in a field "text" (string) instead of an attached payload. In that case, this plugin opens a text editor with the content instead of saving it as a file. If the content transferred is a url, it can be sent in a field "url" (string). In that case, this plugin opens that url in the default browser.