Figured I better set some guidelines now ;-)
For inclusion in CVS you must: a) Follow the user color settings. This means no normal pixmaps, which when used in a dedicated KWin style allow no configuration at all (you can't override the pixmaps and you can't follow the color scheme). KWM themes are for that, at least then everything is configurable. It makes no sense to just make pixmaps then bitblt them, since it is way less functional than KWM themes. If you want to draw decorations first you can use kpixmap2bitmap in kdegraphics to separate the shades and then kColorBitmaps in kdrawutil.h to draw it using a colorgroup from the options class. b) You must follow at least the color settings from the user Options class. svn path=/trunk/kdebase/kwin/; revision=45132
This commit is contained in:
parent
7dd5c805e4
commit
5aad79903d
1 changed files with 20 additions and 0 deletions
20
clients/REQUIREMENTS_FOR_CVS
Normal file
20
clients/REQUIREMENTS_FOR_CVS
Normal file
|
@ -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 the 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
|
||||
|
Loading…
Reference in a new issue