You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ismael Asensio a9a58b1ed5 Port usage of kcmshell5 to kcmshell6
Just two instances:
- in useractions for the menu action "Configure Window Manager"
- in the docbook about the key shortcuts
1 year ago
LICENSES Remove unused license file 2 years ago
autotests autotests: Remove WAYLAND_ONLY leftovers 1 year ago
cmake/modules Drop Qt6WaylandClientMacros.cmake fork 1 year ago
data Port to KF6 2 years ago
doc Port usage of kcmshell5 to kcmshell6 1 year ago
po GIT_SILENT Sync po/docbooks with svn 1 year ago
src Port usage of kcmshell5 to kcmshell6 1 year ago
tests Drop XCB_ICCCM_FOUND checks 1 year ago
.clang-format Run clang-format 3 years ago
.gitignore Run clang-format 3 years ago
.gitlab-ci.yml ci: Bump to Qt 6.5 1 year ago
.kde-ci.yml Add wayland to third-party deps 1 year ago
CMakeLists.txt cmake: Correct gbm version check 1 year ago
CONTRIBUTING.md add more debugging information to CONTRIBUTING.md 2 years ago
KWinDBusInterfaceConfig.cmake.in Expose org.kde.kwin.ColorCorrect.xml dbus file 3 years ago
Mainpage.dox
README.md doc: modernise HACKING -> CONTRIBUTING guidelines and information 3 years ago
logo.png
plasma-kwin_wayland.service.in Re-enable systemd managed kwin 3 years ago
plasma-kwin_x11.service.in [systemd] Fix X11 service file 3 years ago

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.