methods don't have virtual destructors, added the virtual destructors to
get rid of warnings and potential memory leaks

Use prefix instead of postfix de- and increments

Fix KWD appmenu popup position. Recalculate global geometry of the menu position instead of using the one provided by Qt.

Set tabCount to 1 in KCommonDecorationUnstable. It will cause float point exception when set to 0.(LP: #1050776).

Used extern in header files to declare variables there and initialize those and assign the values in the respective .c/.cpp files
Revert some "special" cases
Minor fixes

"http://www.compiz-fusion.org" is not existent anymore and leads one to the "Web Design Manchester" web design business page (used in the About dialogue of CCSM for example) and
"http://www.compiz.org" is outdated and does not reflect actual development of Compiz anymore

Redeclared and reassigned frameType, frameState, frameActions unsigned int variables andalso added those to decor_quads_to_property in the #else branch in KWD::Switcher::updateWindowProperties () (switcher.cpp)

Simplified updateWindowProperties () by removing redundant declaration of the variables 'frameType', 'frameState' and 'frameActions'

It was a broken hack for a problem that didn't exist

decoration interface, until KDE4 Window decorator is re-written to allow
for decoration lists.

Note that this gives public access to KWD::Decorator, which is a bad thing.

The way this works is to create two separate frames for inactive and active
decoration, and when one property is written to update the other.

Previously the switcher window was a normal managed window (which
the switcher plugin actually lied about, see SwitchWindow::managed),
such that the decorators could pick it up and draw the switcher
decoration. However now with reparenting, this means that whenever
we actually manage and unmanage the switcher window (eg with map
and unmap) it means we must also reparent the window, which floods
the server with requests and makes the switcher slow.

Since we don't interact with the switcher window, it makes no sense
to manage it like this, so make it override redirect

Rationale: some window decorators or themes might want to specify a border
input area that is slightly larger than the visible borders on screen
(eg for enhanced resize handles, a11y purposes, etc) or the theme might
want to specify some additional decoration which should affect placement
but should not be interacted with.

In this case we have a priv->border and priv->input window property.
priv->border specifies the actual semantic size of the window decoration
that should affect placement and priv->input specifies the extents of
the frame window past the client.

Fixes LP: #710271

As the default composition mode is SourceOver and the old contents are uninitialized, all sorts of graphical corruption could occur. Fix that by using Source composition mode and thus not using the old contents for blending.

Forward port 50c061b29c9fccdc937f0de92ba1edccab1a05a4 to master

Previously, the pixmaps were recreated as soon as any property changed (and thus way too often), so it would happen that at the time the decoration plugin needs to access the pixmap, it would already have been destroyed. Avoid that by only recreating the pixmaps when needed.

Forward port of edb51e95e959accd3873179a20bc4674c51f5efe to master

Remove the DBUS and GConf based settings retreival. It was long
broken and based on a bunch of old assumptions