2020-03-15 15:19:28 +00:00
|
|
|
/*
|
|
|
|
SPDX-FileCopyrightText: 2017 Marco Martin <notmart@gmail.com>
|
|
|
|
|
|
|
|
SPDX-License-Identifier: LGPL-2.1-only OR LGPL-3.0-only OR LicenseRef-KDE-Accepted-LGPL
|
|
|
|
*/
|
2018-09-12 17:49:38 +00:00
|
|
|
#ifndef KWAYLAND_SERVER_XDGFOREIGNV2_INTERFACE_P_H
|
|
|
|
#define KWAYLAND_SERVER_XDGFOREIGNV2_INTERFACE_P_H
|
Wayland foreign protocol
Summary:
Implement the "foreign" wayland protocol.
A client can export a surface with an unique string as handle,
then another client can refer to that surface and set an own surface as
child of that surface.
Potential use cases are out-of-process dialogs, such as file dialogs,
meant to be used by sandboxed processes that may not have the access
it needs to implement such dialogs.
The handle needs to be shared between the processes with other means,
such as dbus or command line paramenters.
The public api of the server side only tracks parent/child relationships as this is the only data kwin would need it for, the rest of the api is not exported so should be safer from eventual protocol changes
Test Plan:
the autotest works, but has a lot of random crashes when deleting surfaces,
unfortunately backtraces don't tell much and the crashes never occur when running into valgrind
behavior may still be wrong, depending on how the protocol is supposed
to work if more clients try to set the same exported surface as parent
Reviewers: #plasma, #kwin, davidedmundson, graesslin
Reviewed By: #plasma, #kwin, graesslin
Subscribers: davidedmundson, graesslin, plasma-devel, #frameworks
Tags: #frameworks, #plasma_on_wayland
Differential Revision: https://phabricator.kde.org/D7369
2017-10-13 09:29:17 +00:00
|
|
|
|
|
|
|
#include "global.h"
|
|
|
|
#include "resource.h"
|
|
|
|
|
2020-04-29 14:56:38 +00:00
|
|
|
namespace KWaylandServer
|
Wayland foreign protocol
Summary:
Implement the "foreign" wayland protocol.
A client can export a surface with an unique string as handle,
then another client can refer to that surface and set an own surface as
child of that surface.
Potential use cases are out-of-process dialogs, such as file dialogs,
meant to be used by sandboxed processes that may not have the access
it needs to implement such dialogs.
The handle needs to be shared between the processes with other means,
such as dbus or command line paramenters.
The public api of the server side only tracks parent/child relationships as this is the only data kwin would need it for, the rest of the api is not exported so should be safer from eventual protocol changes
Test Plan:
the autotest works, but has a lot of random crashes when deleting surfaces,
unfortunately backtraces don't tell much and the crashes never occur when running into valgrind
behavior may still be wrong, depending on how the protocol is supposed
to work if more clients try to set the same exported surface as parent
Reviewers: #plasma, #kwin, davidedmundson, graesslin
Reviewed By: #plasma, #kwin, graesslin
Subscribers: davidedmundson, graesslin, plasma-devel, #frameworks
Tags: #frameworks, #plasma_on_wayland
Differential Revision: https://phabricator.kde.org/D7369
2017-10-13 09:29:17 +00:00
|
|
|
{
|
|
|
|
|
|
|
|
class Display;
|
|
|
|
class SurfaceInterface;
|
|
|
|
class XdgExportedUnstableV2Interface;
|
|
|
|
class XdgImportedUnstableV2Interface;
|
|
|
|
|
|
|
|
class Q_DECL_HIDDEN XdgForeignInterface::Private
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
Private(Display *display, XdgForeignInterface *q);
|
|
|
|
|
|
|
|
XdgForeignInterface *q;
|
|
|
|
XdgExporterUnstableV2Interface *exporter;
|
|
|
|
XdgImporterUnstableV2Interface *importer;
|
|
|
|
};
|
|
|
|
|
|
|
|
class Q_DECL_HIDDEN XdgExporterUnstableV2Interface : public Global
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
virtual ~XdgExporterUnstableV2Interface();
|
|
|
|
|
|
|
|
XdgExportedUnstableV2Interface *exportedSurface(const QString &handle);
|
|
|
|
|
|
|
|
Q_SIGNALS:
|
|
|
|
void surfaceExported(const QString &handle, XdgExportedUnstableV2Interface *exported);
|
|
|
|
void surfaceUnexported(const QString &handle);
|
|
|
|
|
|
|
|
private:
|
|
|
|
explicit XdgExporterUnstableV2Interface(Display *display, XdgForeignInterface *parent = nullptr);
|
|
|
|
friend class Display;
|
|
|
|
friend class XdgForeignInterface;
|
|
|
|
class Private;
|
|
|
|
Private *d_func() const;
|
|
|
|
};
|
|
|
|
|
|
|
|
class Q_DECL_HIDDEN XdgImporterUnstableV2Interface : public Global
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
virtual ~XdgImporterUnstableV2Interface();
|
|
|
|
|
|
|
|
XdgImportedUnstableV2Interface *importedSurface(const QString &handle);
|
|
|
|
SurfaceInterface *transientFor(SurfaceInterface *surface);
|
|
|
|
|
|
|
|
Q_SIGNALS:
|
|
|
|
void surfaceImported(const QString &handle, XdgImportedUnstableV2Interface *imported);
|
|
|
|
void surfaceUnimported(const QString &handle);
|
2020-04-29 14:56:38 +00:00
|
|
|
void transientChanged(KWaylandServer::SurfaceInterface *child, KWaylandServer::SurfaceInterface *parent);
|
Wayland foreign protocol
Summary:
Implement the "foreign" wayland protocol.
A client can export a surface with an unique string as handle,
then another client can refer to that surface and set an own surface as
child of that surface.
Potential use cases are out-of-process dialogs, such as file dialogs,
meant to be used by sandboxed processes that may not have the access
it needs to implement such dialogs.
The handle needs to be shared between the processes with other means,
such as dbus or command line paramenters.
The public api of the server side only tracks parent/child relationships as this is the only data kwin would need it for, the rest of the api is not exported so should be safer from eventual protocol changes
Test Plan:
the autotest works, but has a lot of random crashes when deleting surfaces,
unfortunately backtraces don't tell much and the crashes never occur when running into valgrind
behavior may still be wrong, depending on how the protocol is supposed
to work if more clients try to set the same exported surface as parent
Reviewers: #plasma, #kwin, davidedmundson, graesslin
Reviewed By: #plasma, #kwin, graesslin
Subscribers: davidedmundson, graesslin, plasma-devel, #frameworks
Tags: #frameworks, #plasma_on_wayland
Differential Revision: https://phabricator.kde.org/D7369
2017-10-13 09:29:17 +00:00
|
|
|
|
|
|
|
private:
|
|
|
|
explicit XdgImporterUnstableV2Interface(Display *display, XdgForeignInterface *parent = nullptr);
|
|
|
|
friend class Display;
|
|
|
|
friend class XdgForeignInterface;
|
|
|
|
class Private;
|
|
|
|
Private *d_func() const;
|
|
|
|
};
|
|
|
|
|
|
|
|
class Q_DECL_HIDDEN XdgExportedUnstableV2Interface : public Resource
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
virtual ~XdgExportedUnstableV2Interface();
|
|
|
|
|
|
|
|
private:
|
|
|
|
explicit XdgExportedUnstableV2Interface(XdgExporterUnstableV2Interface *parent, wl_resource *parentResource);
|
|
|
|
friend class XdgExporterUnstableV2Interface;
|
|
|
|
|
|
|
|
class Private;
|
|
|
|
Private *d_func() const;
|
|
|
|
};
|
|
|
|
|
|
|
|
class Q_DECL_HIDDEN XdgImportedUnstableV2Interface : public Resource
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
public:
|
|
|
|
virtual ~XdgImportedUnstableV2Interface();
|
|
|
|
|
|
|
|
SurfaceInterface *child() const;
|
|
|
|
|
|
|
|
Q_SIGNALS:
|
2020-04-29 14:56:38 +00:00
|
|
|
void childChanged(KWaylandServer::SurfaceInterface *child);
|
Wayland foreign protocol
Summary:
Implement the "foreign" wayland protocol.
A client can export a surface with an unique string as handle,
then another client can refer to that surface and set an own surface as
child of that surface.
Potential use cases are out-of-process dialogs, such as file dialogs,
meant to be used by sandboxed processes that may not have the access
it needs to implement such dialogs.
The handle needs to be shared between the processes with other means,
such as dbus or command line paramenters.
The public api of the server side only tracks parent/child relationships as this is the only data kwin would need it for, the rest of the api is not exported so should be safer from eventual protocol changes
Test Plan:
the autotest works, but has a lot of random crashes when deleting surfaces,
unfortunately backtraces don't tell much and the crashes never occur when running into valgrind
behavior may still be wrong, depending on how the protocol is supposed
to work if more clients try to set the same exported surface as parent
Reviewers: #plasma, #kwin, davidedmundson, graesslin
Reviewed By: #plasma, #kwin, graesslin
Subscribers: davidedmundson, graesslin, plasma-devel, #frameworks
Tags: #frameworks, #plasma_on_wayland
Differential Revision: https://phabricator.kde.org/D7369
2017-10-13 09:29:17 +00:00
|
|
|
|
|
|
|
private:
|
|
|
|
explicit XdgImportedUnstableV2Interface(XdgImporterUnstableV2Interface *parent, wl_resource *parentResource);
|
|
|
|
friend class XdgImporterUnstableV2Interface;
|
|
|
|
|
|
|
|
class Private;
|
|
|
|
Private *d_func() const;
|
|
|
|
};
|
|
|
|
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|