8f6edea521
krunner stuff doesn't really belong in kwin, it has nothing to do with compositing or any other things that are the domain of compositors. Given that, being as a plugin suits the krunner integration stuff best.
38 lines
798 B
C++
38 lines
798 B
C++
/*
|
|
SPDX-FileCopyrightText: 2020 Vlad Zahorodnii <vlad.zahorodnii@kde.org>
|
|
|
|
SPDX-License-Identifier: GPL-2.0-or-later
|
|
*/
|
|
|
|
#include "windowsrunnerinterface.h"
|
|
#include "main.h"
|
|
|
|
#include <KPluginFactory>
|
|
|
|
using namespace KWin;
|
|
|
|
class KWIN_EXPORT KRunnerIntegrationFactory : public PluginFactory
|
|
{
|
|
Q_OBJECT
|
|
Q_PLUGIN_METADATA(IID PluginFactory_iid FILE "metadata.json")
|
|
Q_INTERFACES(KWin::PluginFactory)
|
|
|
|
public:
|
|
explicit KRunnerIntegrationFactory(QObject *parent = nullptr);
|
|
|
|
Plugin *create() const override;
|
|
};
|
|
|
|
KRunnerIntegrationFactory::KRunnerIntegrationFactory(QObject *parent)
|
|
: PluginFactory(parent)
|
|
{
|
|
}
|
|
|
|
Plugin *KRunnerIntegrationFactory::create() const
|
|
{
|
|
return new WindowsRunner();
|
|
}
|
|
|
|
K_EXPORT_PLUGIN_VERSION(KWIN_PLUGIN_API_VERSION)
|
|
|
|
#include "main.moc"
|