From 0b6057404f65218182ab27a9483a21065ef61fca Mon Sep 17 00:00:00 2001 From: Timothy Pearson Date: Mon, 7 Nov 2011 21:50:33 -0600 Subject: Rename kwin to twin (Part 2 of 2) --- twin/clients/REQUIREMENTS_FOR_CVS | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 twin/clients/REQUIREMENTS_FOR_CVS (limited to 'twin/clients/REQUIREMENTS_FOR_CVS') diff --git a/twin/clients/REQUIREMENTS_FOR_CVS b/twin/clients/REQUIREMENTS_FOR_CVS new file mode 100644 index 000000000..778e2fe2d --- /dev/null +++ b/twin/clients/REQUIREMENTS_FOR_CVS @@ -0,0 +1,20 @@ +If you are looking to include a C++ KWin style client in CVS make sure you +follow the following requirements: + +A) You must follow the current color scheme for all decorations. *No* fixed +pixmaps are allowed for the clients. If you wish to draw your decorations +use as few shades as possible, then use kpixmap2bitmap in kdegraphics +to convert them into individual bitmaps. Once this is done you can +draw the bitmaps using a colorgroup with kColorBitmaps. + +If your client is just a set of pixmaps that doesn't follow any of the options +I suggest you make a KWM theme so the user gets those options to +configure the pixmaps and look. Making a plain pixmapped dedicated style +makes no sense since it is less configurable than KWM themes and cannot follow +client plugin options. + +B) You must follow at least the color settings in the Options class. + +Daniel M. Duley +mosfet@kde.org + -- cgit v1.2.1