My KWIN fork where I work on features like per-output virtual desktops
Find a file
Xaver Hugl 6bd07ad6b3 backends/drm: remove the shadow buffer when possible, and reduce it to 10bpc when not
Using the custom values for min. and max. luminance in transfer functions, we can reduce the
ranges of values in the shadow buffer to be limited to [0, 1], and with that we can switch
from a floating point buffer back to a normalized format. As gamma 2.2 encoding is much more
efficient at storing color values, this also drops the buffer from 16bpc down to 10bpc.

Furthermore, this offloads the gamma 2.2 -> PQ conversion to KMS when possible, and then uses
the scanout buffer with gamma 2.2 encoding directly. This way the shadow buffer gets completely
skipped and performance and efficiency get improved a lot.

BUG: 491452
CCBUG: 477223
2024-08-09 15:18:43 +02:00
autotests backends/drm: remove the shadow buffer when possible, and reduce it to 10bpc when not 2024-08-09 15:18:43 +02:00
cmake/modules xwayland: Enable xtest libei integration 2024-05-15 09:31:53 +00:00
data
doc docs: update testing instructions 2024-07-11 13:56:23 +00:00
examples
kconf_update Remove orphan shortcuts for desktop grid and expose effects 2024-06-04 10:09:08 +00:00
LICENSES
po GIT_SILENT Sync po/docbooks with svn 2024-08-09 01:30:10 +00:00
src backends/drm: remove the shadow buffer when possible, and reduce it to 10bpc when not 2024-08-09 15:18:43 +02:00
tests
.clang-format bump clang-format to C++ 20 2024-07-04 16:29:25 +02:00
.gitignore
.gitlab-ci.yml Revert "Disable freebsd ci" 2024-05-02 09:39:13 +00:00
.kde-ci.yml
CMakeLists.txt utils: Add support for svg cursors 2024-08-07 11:57:39 +03:00
CONTRIBUTING.md docs/contributing: Update windowswitchers location 2024-05-15 18:36:46 +02:00
KWinDBusInterfaceConfig.cmake.in
logo.png
Mainpage.dox
plasma-kwin_wayland.service.in
plasma-kwin_x11.service.in
README.md

KWin

KWin is an easy to use, but flexible, composited Window Manager for Xorg windowing systems (Wayland, X11) on Linux. Its primary usage is in conjunction with a Desktop Shell (e.g. KDE Plasma Desktop). KWin is designed to go out of the way; users should not notice that they use a window manager at all. Nevertheless KWin provides a steep learning curve for advanced features, which are available, if they do not conflict with the primary mission. KWin does not have a dedicated targeted user group, but follows the targeted user group of the Desktop Shell using KWin as it's window manager.

KWin is not...

  • a standalone window manager (c.f. openbox, i3) and does not provide any functionality belonging to a Desktop Shell.
  • a replacement for window managers designed for use with a specific Desktop Shell (e.g. GNOME Shell)
  • a minimalistic window manager
  • designed for use without compositing or for X11 network transparency, though both are possible.

Contributing to KWin

Please refer to the contributing document for everything you need to know to get started contributing to KWin.

Contacting KWin development team

  • mailing list: kwin@kde.org
  • IRC: #kde-kwin on irc.libera.chat

Support

Application Developer

If you are an application developer having questions regarding windowing systems (either X11 or Wayland) please do not hesitate to contact us. Preferable through our mailing list. Ideally subscribe to the mailing list, so that your mail doesn't get stuck in the moderation queue.

End user

Please contact the support channels of your Linux distribution for user support. The KWin development team does not provide end user support.

Reporting bugs

Please use KDE's bugtracker and report for product KWin.

Guidelines for new features

A new Feature can only be added to KWin if:

  • it does not violate the primary missions as stated at the start of this document
  • it does not introduce instabilities
  • it is maintained, that is bugs are fixed in a timely manner (second next minor release) if it is not a corner case.
  • it works together with all existing features
  • it supports both single and multi screen (xrandr)
  • it adds a significant advantage
  • it is feature complete, that is supports at least all useful features from competitive implementations
  • it is not a special case for a small user group
  • it does not increase code complexity significantly
  • it does not affect KWin's license (GPLv2+)

All new added features are under probation, that is if any of the non-functional requirements as listed above do not hold true in the next two feature releases, the added feature will be removed again.

The same non functional requirements hold true for any kind of plugins (effects, scripts, etc.). It is suggested to use scripted plugins and distribute them separately.