Toggle the table of contents

Projects/KWin: Difference between revisions

From KDE TechBase

Revision as of 10:37, 2 November 2008

This is a starting page for all relevant KWin documentation, most of which is stored in SVN or on external WWW pages.

General information

KWin mailing list
COMPLIANCE - a document on KWin's compliance to the window manager specifications ICCCM and EWMH (also known as NETWM).
KDE4.0 release notes - information about changes and new features in KWin in KDE4.0

Developer information

HACKING - Starting document for developers interested in helping with developing KWin, including information on the KWin mailing list, KWin structure, developing tips, etc.
libkdecoration API documentation - API documentation for the library used for developing KWin decorations (the link points to documentation for the current development version, for other versions: 4.0 ).
clients/PORTING - List of changes needed to port decorations from KDE3 to KDE4.
KWin decorations HOWTO - tutorial on writing KWin decorations. Based on KDE3.2 and as such slightly outdated, but it is still usable for newer versions (see also the PORTING document above). Note that current decorations should use KCommonDecoration class instead of KDecoration directly like this tutorial does.
COMPOSITE_TODO - TODO list for compositing support in KWin.
libkwineffects API documentation - Documentation on API for compositing effects - currently needs to be done, developers interested in developing compositing effects for KWin are currently suggested to use source of already existing effects shipped with KWin (especially the Howto effect in the tests/ directory as a starting point) and/or ask on the KWin mailing list if necessary. NOTE: This API is currently considered unstable and subject to change.

Configuration

COMPOSITE_HOWTO - document on setting up support for compositing feature of KWin (X.Org configuration, driver issues, etc.).
CONFIGURING - document on advanced KWin configuration (such as pre-configuring window-specific settings).

Various

HW list - information about various hardware and KWin (mainly in relation to compositing support)

Retrieved from "https://techbase.kde.org/index.php?title=Projects/KWin&oldid=35246"

@@ Line 12: / Line 12: @@
 * [http://api.kde.org/4.x-api/kdebase-workspace-apidocs/kwin/lib/html/group__kdecoration.html libkdecoration API documentation] - API documentation for the library used for developing KWin decorations (the link points to documentation for the current development version, for other versions: [http://api.kde.org/4.0-api/kdebase-workspace-apidocs/kwin/lib/html/group__kdecoration.html 4.0] ).
 * [http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/clients/PORTING clients/PORTING] - List of changes needed to port decorations from KDE3 to KDE4.
-* [http://www.usermode.org/docs/kwintheme.html KWin decorations HOWTO] - tutorial on writing KWin decorations. Note that it is written for KDE3.2, but it is also usable for newer versions (see also the PORTING document above)
+* [http://www.usermode.org/docs/kwintheme.html KWin decorations HOWTO] - tutorial on writing KWin decorations. Based on KDE3.2 and as such slightly outdated, but it is still usable for newer versions (see also the PORTING document above). Note that current decorations should use KCommonDecoration class instead of KDecoration directly like this tutorial does.
 * [http://websvn.kde.org/*checkout*/trunk/KDE/kdebase/workspace/kwin/COMPOSITE_TODO COMPOSITE_TODO ] - TODO list for compositing support in KWin.
 * [http://api.kde.org/4.x-api/kdebase-workspace-apidocs/kwin/lib/html/group__kwineffects.html libkwineffects API documentation ] - Documentation on API for compositing effects - currently needs to be done, developers interested in developing compositing effects for KWin are currently suggested to use source of already [http://websvn.kde.org/trunk/KDE/kdebase/workspace/kwin/effects/ existing effects shipped with KWin] (especially the Howto effect in the tests/ directory as a starting point) and/or ask on the KWin mailing list if necessary. NOTE: This API is currently considered unstable and subject to change.