-
-
Notifications
You must be signed in to change notification settings - Fork 849
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
kde-server-decoration: move to new impl
- Loading branch information
Showing
9 changed files
with
205 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,85 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <protocol name="server_decoration"> | ||
| <copyright><![CDATA[ | ||
| SPDX-FileCopyrightText: 2015 Martin Gräßlin | ||
| SPDX-License-Identifier: LGPL-2.1-or-later | ||
| ]]></copyright> | ||
| <interface name="org_kde_kwin_server_decoration_manager" version="1"> | ||
| <description summary="Server side window decoration manager"> | ||
| This interface allows to coordinate whether the server should create | ||
| a server-side window decoration around a wl_surface representing a | ||
| shell surface (wl_shell_surface or similar). By announcing support | ||
| for this interface the server indicates that it supports server | ||
| side decorations. | ||
|
|
||
| Use in conjunction with zxdg_decoration_manager_v1 is undefined. | ||
| </description> | ||
| <request name="create"> | ||
| <description summary="Create a server-side decoration object for a given surface"> | ||
| When a client creates a server-side decoration object it indicates | ||
| that it supports the protocol. The client is supposed to tell the | ||
| server whether it wants server-side decorations or will provide | ||
| client-side decorations. | ||
|
|
||
| If the client does not create a server-side decoration object for | ||
| a surface the server interprets this as lack of support for this | ||
| protocol and considers it as client-side decorated. Nevertheless a | ||
| client-side decorated surface should use this protocol to indicate | ||
| to the server that it does not want a server-side deco. | ||
| </description> | ||
| <arg name="id" type="new_id" interface="org_kde_kwin_server_decoration"/> | ||
| <arg name="surface" type="object" interface="wl_surface"/> | ||
| </request> | ||
| <enum name="mode"> | ||
| <description summary="Possible values to use in request_mode and the event mode."/> | ||
| <entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/> | ||
| <entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/> | ||
| <entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/> | ||
| </enum> | ||
| <event name="default_mode"> | ||
| <description summary="The default mode used on the server"> | ||
| This event is emitted directly after binding the interface. It contains | ||
| the default mode for the decoration. When a new server decoration object | ||
| is created this new object will be in the default mode until the first | ||
| request_mode is requested. | ||
|
|
||
| The server may change the default mode at any time. | ||
| </description> | ||
| <arg name="mode" type="uint" summary="The default decoration mode applied to newly created server decorations."/> | ||
| </event> | ||
| </interface> | ||
| <interface name="org_kde_kwin_server_decoration" version="1"> | ||
| <request name="release" type="destructor"> | ||
| <description summary="release the server decoration object"/> | ||
| </request> | ||
| <enum name="mode"> | ||
| <description summary="Possible values to use in request_mode and the event mode."/> | ||
| <entry name="None" value="0" summary="Undecorated: The surface is not decorated at all, neither server nor client-side. An example is a popup surface which should not be decorated."/> | ||
| <entry name="Client" value="1" summary="Client-side decoration: The decoration is part of the surface and the client."/> | ||
| <entry name="Server" value="2" summary="Server-side decoration: The server embeds the surface into a decoration frame."/> | ||
| </enum> | ||
| <request name="request_mode"> | ||
| <description summary="The decoration mode the surface wants to use."/> | ||
| <arg name="mode" type="uint" summary="The mode this surface wants to use."/> | ||
| </request> | ||
| <event name="mode"> | ||
| <description summary="The new decoration mode applied by the server"> | ||
| This event is emitted directly after the decoration is created and | ||
| represents the base decoration policy by the server. E.g. a server | ||
| which wants all surfaces to be client-side decorated will send Client, | ||
| a server which wants server-side decoration will send Server. | ||
|
|
||
| The client can request a different mode through the decoration request. | ||
| The server will acknowledge this by another event with the same mode. So | ||
| even if a server prefers server-side decoration it's possible to force a | ||
| client-side decoration. | ||
|
|
||
| The server may emit this event at any time. In this case the client can | ||
| again request a different mode. It's the responsibility of the server to | ||
| prevent a feedback loop. | ||
| </description> | ||
| <arg name="mode" type="uint" summary="The decoration mode applied to the surface by the server."/> | ||
| </event> | ||
| </interface> | ||
| </protocol> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,53 @@ | ||
| #include "ServerDecorationKDE.hpp" | ||
|
|
||
| #define LOGM PROTO::serverDecorationKDE->protoLog | ||
|
|
||
| CServerDecorationKDE::CServerDecorationKDE(SP<COrgKdeKwinServerDecoration> resource_, wlr_surface* surf) : resource(resource_) { | ||
| if (!good()) | ||
| return; | ||
|
|
||
| resource->setRelease([this](COrgKdeKwinServerDecoration* pMgr) { PROTO::serverDecorationKDE->destroyResource(this); }); | ||
| resource->setOnDestroy([this](COrgKdeKwinServerDecoration* pMgr) { PROTO::serverDecorationKDE->destroyResource(this); }); | ||
|
|
||
| // we send this and ignore request_mode. | ||
| resource->sendMode(ORG_KDE_KWIN_SERVER_DECORATION_MANAGER_MODE_SERVER); | ||
| } | ||
|
|
||
| bool CServerDecorationKDE::good() { | ||
| return resource->resource(); | ||
| } | ||
|
|
||
| CServerDecorationKDEProtocol::CServerDecorationKDEProtocol(const wl_interface* iface, const int& ver, const std::string& name) : IWaylandProtocol(iface, ver, name) { | ||
| ; | ||
| } | ||
|
|
||
| void CServerDecorationKDEProtocol::bindManager(wl_client* client, void* data, uint32_t ver, uint32_t id) { | ||
| const auto RESOURCE = m_vManagers.emplace_back(std::make_unique<COrgKdeKwinServerDecorationManager>(client, ver, id)).get(); | ||
| RESOURCE->setOnDestroy([this](COrgKdeKwinServerDecorationManager* p) { this->onManagerResourceDestroy(p->resource()); }); | ||
|
|
||
| RESOURCE->setCreate([this](COrgKdeKwinServerDecorationManager* pMgr, uint32_t id, wl_resource* pointer) { this->createDecoration(pMgr, id, pointer); }); | ||
|
|
||
| // send default mode of SSD, as Hyprland will never ask for CSD. Screw Gnome and GTK. | ||
| RESOURCE->sendDefaultMode(ORG_KDE_KWIN_SERVER_DECORATION_MANAGER_MODE_SERVER); | ||
| } | ||
|
|
||
| void CServerDecorationKDEProtocol::onManagerResourceDestroy(wl_resource* res) { | ||
| std::erase_if(m_vManagers, [&](const auto& other) { return other->resource() == res; }); | ||
| } | ||
|
|
||
| void CServerDecorationKDEProtocol::destroyResource(CServerDecorationKDE* hayperlaaaand) { | ||
| std::erase_if(m_vDecos, [&](const auto& other) { return other.get() == hayperlaaaand; }); | ||
| } | ||
|
|
||
| void CServerDecorationKDEProtocol::createDecoration(COrgKdeKwinServerDecorationManager* pMgr, uint32_t id, wl_resource* surf) { | ||
| const auto CLIENT = pMgr->client(); | ||
| const auto RESOURCE = | ||
| m_vDecos.emplace_back(std::make_unique<CServerDecorationKDE>(std::make_shared<COrgKdeKwinServerDecoration>(CLIENT, pMgr->version(), id), wlr_surface_from_resource(surf))) | ||
| .get(); | ||
|
|
||
| if (!RESOURCE->good()) { | ||
| pMgr->noMemory(); | ||
| m_vDecos.pop_back(); | ||
| return; | ||
| } | ||
| } |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| #pragma once | ||
|
|
||
| #include <memory> | ||
| #include <vector> | ||
| #include <cstdint> | ||
| #include "WaylandProtocol.hpp" | ||
| #include "kde-server-decoration.hpp" | ||
|
|
||
| class CServerDecorationKDE { | ||
| public: | ||
| CServerDecorationKDE(SP<COrgKdeKwinServerDecoration> resource_, wlr_surface* surf); | ||
|
|
||
| bool good(); | ||
|
|
||
| private: | ||
| SP<COrgKdeKwinServerDecoration> resource; | ||
| }; | ||
|
|
||
| class CServerDecorationKDEProtocol : public IWaylandProtocol { | ||
| public: | ||
| CServerDecorationKDEProtocol(const wl_interface* iface, const int& ver, const std::string& name); | ||
|
|
||
| virtual void bindManager(wl_client* client, void* data, uint32_t ver, uint32_t id); | ||
|
|
||
| private: | ||
| void onManagerResourceDestroy(wl_resource* res); | ||
| void destroyResource(CServerDecorationKDE* deco); | ||
|
|
||
| void createDecoration(COrgKdeKwinServerDecorationManager* pMgr, uint32_t id, wl_resource* surf); | ||
|
|
||
| // | ||
| std::vector<UP<COrgKdeKwinServerDecorationManager>> m_vManagers; | ||
| std::vector<UP<CServerDecorationKDE>> m_vDecos; | ||
|
|
||
| friend class CServerDecorationKDE; | ||
| }; | ||
|
|
||
| namespace PROTO { | ||
| inline UP<CServerDecorationKDEProtocol> serverDecorationKDE; | ||
| }; |