yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/src/renderbackend.h

39 lines
809 B
C
Raw Normal View History

Introduce explicit base render backend type The main idea behind the render backend is to decouple low level bits from scenes. The end goal is to make the render backend provide render targets where the scene can render. Design-wise, such a split is more flexible than the current state, for example we could start experimenting with using qtquick (assuming that the legacy scene is properly encapsulated) or creating multiple scenes, for example for each output layer, etc. So far, the RenderBackend class only contains one getter, more stuff will be moved from the Scene as it makes sense.
2021-11-10 10:34:18 +00:00
/*
SPDX-FileCopyrightText: 2021 Vlad Zahorodnii <vlad.zahorodnii@kde.org>
SPDX-License-Identifier: GPL-2.0-or-later
*/
#pragma once
#include "kwinglobals.h"
#include <QObject>
namespace KWin
{
Unify beginFrame() and endFrame() hooks for OpenGL and QPainter backends This unifies frame hooks for OpenGL and QPainter render backends. There are a couple of reasons why it's a good idea - it provides one mental framework to start painting a frame, the Compositor will be able to start and submit frames. The last one is very cool because it gives the Compositor more power over compositing. Besides unifying frame hooks, this cleans up a bit the arg naming mess in endFrame(). As is, "damage" and "damagedRegion" are very confusing names. "damage" arg has been renamed to "renderedRegion," because that's what it is. The renderedRegion arg specifies the region that has been repainted by the Scene. It's different from the damagedRegion as that one specifies the surface damage, i.e. the difference between the current and the next frame, while the renderedRegion may include a region that had to be repainted to repair the back buffer. The main reason why we need renderedRegion is the X11 platform. On Wayland, it's unused. In the future, we will need to extend this api with output layers.
2021-11-11 11:24:02 +00:00
class AbstractOutput;
Move OverlayWindow getter to RenderBackend
2021-11-11 09:48:43 +00:00
class OverlayWindow;
Introduce explicit base render backend type The main idea behind the render backend is to decouple low level bits from scenes. The end goal is to make the render backend provide render targets where the scene can render. Design-wise, such a split is more flexible than the current state, for example we could start experimenting with using qtquick (assuming that the legacy scene is properly encapsulated) or creating multiple scenes, for example for each output layer, etc. So far, the RenderBackend class only contains one getter, more stuff will be moved from the Scene as it makes sense.
2021-11-10 10:34:18 +00:00
/**
* The RenderBackend class is the base class for all rendering backends.
*/
class KWIN_EXPORT RenderBackend : public QObject
{
Q_OBJECT
public:
explicit RenderBackend(QObject *parent = nullptr);
virtual CompositingType compositingType() const = 0;
Move OverlayWindow getter to RenderBackend
2021-11-11 09:48:43 +00:00
virtual OverlayWindow *overlayWindow() const;
Unify beginFrame() and endFrame() hooks for OpenGL and QPainter backends This unifies frame hooks for OpenGL and QPainter render backends. There are a couple of reasons why it's a good idea - it provides one mental framework to start painting a frame, the Compositor will be able to start and submit frames. The last one is very cool because it gives the Compositor more power over compositing. Besides unifying frame hooks, this cleans up a bit the arg naming mess in endFrame(). As is, "damage" and "damagedRegion" are very confusing names. "damage" arg has been renamed to "renderedRegion," because that's what it is. The renderedRegion arg specifies the region that has been repainted by the Scene. It's different from the damagedRegion as that one specifies the surface damage, i.e. the difference between the current and the next frame, while the renderedRegion may include a region that had to be repainted to repair the back buffer. The main reason why we need renderedRegion is the X11 platform. On Wayland, it's unused. In the future, we will need to extend this api with output layers.
2021-11-11 11:24:02 +00:00
Move graphics reset handling to RenderBackend This makes the Scene less overloaded and it's needed for things such as render layers. In hindsight, it would be great to merge checkGraphicsReset() and beginFrame(), e.g. make beginFrame() return the status like in QRhi or VkSwapchain. If it's OUT_OF_DATE or something, reinitialize the compositor.
2021-12-31 11:51:42 +00:00
virtual bool checkGraphicsReset();
Unify beginFrame() and endFrame() hooks for OpenGL and QPainter backends This unifies frame hooks for OpenGL and QPainter render backends. There are a couple of reasons why it's a good idea - it provides one mental framework to start painting a frame, the Compositor will be able to start and submit frames. The last one is very cool because it gives the Compositor more power over compositing. Besides unifying frame hooks, this cleans up a bit the arg naming mess in endFrame(). As is, "damage" and "damagedRegion" are very confusing names. "damage" arg has been renamed to "renderedRegion," because that's what it is. The renderedRegion arg specifies the region that has been repainted by the Scene. It's different from the damagedRegion as that one specifies the surface damage, i.e. the difference between the current and the next frame, while the renderedRegion may include a region that had to be repainted to repair the back buffer. The main reason why we need renderedRegion is the X11 platform. On Wayland, it's unused. In the future, we will need to extend this api with output layers.
2021-11-11 11:24:02 +00:00
virtual QRegion beginFrame(AbstractOutput *output) = 0;
virtual void endFrame(AbstractOutput *output, const QRegion &renderedRegion, const QRegion &damagedRegion) = 0;
Introduce explicit base render backend type The main idea behind the render backend is to decouple low level bits from scenes. The end goal is to make the render backend provide render targets where the scene can render. Design-wise, such a split is more flexible than the current state, for example we could start experimenting with using qtquick (assuming that the legacy scene is properly encapsulated) or creating multiple scenes, for example for each output layer, etc. So far, the RenderBackend class only contains one getter, more stuff will be moved from the Scene as it makes sense.
2021-11-10 10:34:18 +00:00
};
} // namespace KWin
Reference in a new issue Copy permalink