summaryrefslogtreecommitdiffstats
path: root/twin/clients/REQUIREMENTS_FOR_CVS
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-07 21:50:33 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-07 21:50:33 -0600
commit0b6057404f65218182ab27a9483a21065ef61fca (patch)
treeb8b06dfa2deb965bebfbe131a772124e3e693a96 /twin/clients/REQUIREMENTS_FOR_CVS
parent43d99cc2477266cb9072e179137f0e8485370b3d (diff)
downloadtdebase-0b6057404f65218182ab27a9483a21065ef61fca.tar.gz
tdebase-0b6057404f65218182ab27a9483a21065ef61fca.zip
Rename kwin to twin (Part 2 of 2)
Diffstat (limited to 'twin/clients/REQUIREMENTS_FOR_CVS')
-rw-r--r--twin/clients/REQUIREMENTS_FOR_CVS20
1 files changed, 20 insertions, 0 deletions
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
+