0.5 New! Added wheel event support (contributed by Knut Morten Johansson, many thanks), fixed a few outstanding bugs, and bumped template to 0.2 including a complete images change. Read the ChangeLog!
0.4 adds a new configuration dialog to the generated window decorations as well as colorizing support (See screenshot 2).
With 0.3, decgen brings full automation to KDE window decoration generation. Prior to 0.3, after generating the header (super.h), it would have had to be integrated into the source tree manually. Now just run automerge and build your tree. If you can build a mockup, you can build a window decoration.
You'll need png2qrgb 0.3 and the decgen 0.4 download. And decent gimp'ing skills.
Pay attention to README, CREATE, and COLORIZING within the decgen distribution. Any improved documentation, script hacks, or engine improvements, send them along.
Thank you come again.
"The bazaar software model doesn't work so well with everyone taking and not contributing back." - FyodorLast changelog:
2007-01-8 Nick Bargnesi * tagged version 0.5
* template-0.2/kwin/template.h: mark-up the TOPSPACING variable
* template-0.2/kwin/template.cpp: modified to remove the help button as the enfants decoration makes no use of it
* template-0.2/kwin/template.cpp: modified updateMask() to support the enfants decoration
* images/*: defaulted to the enfants window decoration
2006-01-5 Nick Bargnesi
* template-0.2/kwin/template.h, template-0.2/kwin/template.cpp: added WheelEvent support (TemplateClient::WheelEvent(QWheelEvent)) from Knut Morten Johansson
* template-0.1.tar.bz2: migrated to version 0.2 with mouse wheel event support
2005-09-11 Nick Bargnesi
* AUTHOR: added AUTHOR
* COLORIZING: added COLORIZING description
* template-0.1/kwin/config/templateconfig.ui: support colorizing options, added tooltips, remade the configuration dialog * template-0.1/kwin/temmplate.cpp: support colorizing, respecting KDE's color settings
* CREATE: fixed more typos, probably introduced others, and added documentation for automerge.sh
* automerge.sh: added automerge.sh to automate the tiles.h.stripped step * CREATE: clarified instructions to _not_ overwrite tiles.h.stripped and ensure to save as tiles.h instead * generate-header.sh: bail out if a super.h header already exists
* CREATE: fixed a typo
* transform.sh: Added -e option to transform script to support the enable-libsuffix options to configure
* src/png2qrgb.cpp: Added error checking, verbose usage information, and the --attr-only option to generate image width, height, names * src/png2qrgb.1: Modified the man page source to reflect the new attr-only option.
when I ported over an old windows theme with decgen 0.5, I noticed often (not always) the images were displayed in a blueish hue, instead of the original colour. what causes this?
Does anyone else notice that this guy has a HUGE desktop? I mean, I'm running 1900x1200, and I'm pretty sure he's bigger. Where do you find a monitor to support that?
hi,
doing a ../../automerge.sh ../../images/super.h on a current kubuntu I get:
industrie13@Cylonix:~/Speicher/Programme/decgen-0.5/cylonminimal-0.1/kwin$ ../../automerge.sh ../../images/super.h
-en Found a valid super.h file (../../images/super.h).
../../automerge.sh: 37: let: not found
head: ../../images/super.h: ungültige Anzahl von Zeilen
../../automerge.sh: 39: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
test: 51: 26: unexpected operator
../../automerge.sh: 51: let: not found
-en Created tiles.h. All done.
without the super.h merged into tiles.h, any ideas?
Hello there,
Alphacube decoration, which is generated with DecGen has a wrong FSF address in its Alphacube.[cpp,h] files. Could you please fix that?
Also the config widget isn't working at least in here, but seems to work in your screenshots, so it might have been fixed... Just wanted to inform you about these.
Thanks.
Really like the idea of DecGen and have been using it.
Various people have asked for additional buttons. Is there a way to add additional buttons to those included in the images folder?
Thanks for your help in advance...
Absolutely possible, but the engine is only setup to support the standard buttons. I'd like to add support, but I've got other F/OSS projects higher priorities right now. And I'm just squeaking out a 0.5 build tonight.
Anyone using 0.4 generated trees, I'm interested to see if you've got any issues when logging out of KDE and back in.
Specifically, do the color settings get reset? Example, I've got a tree I added colorizing to, and I default to using KDE's color settings even when I selected the theme's colors.
I ask this question with all due respect to both authors, but what exactly is the difference / advantages / disadvantages and or functionality difference between the two utilities ? I ask this, just in case I'm missing something, I'm going to install decgen and give it a whirl with some of the decos I have produced for deKorator,
The main difference is that decgen is a set of tools allowing you to make a native window decoration, it transforms the images into code. The reason I prefer this is that settings such as button placement, spacing, caption height, app-icon placement, and many other things can be edited easily. Another reason I prefer decgen is that the packages are put together neatly and you don't have to keep track of image directories. I don't mean to say that deKorator isn't a good tool, just pointing out some of the benefits of decgen.
Well, I think currently we've got three processes for making window decoration, and that's 2+ over what we had last time, so progress is good.
Method 1) Start from scratch (or a tutorial like http://www.usermode.org/docs/kwintheme.html)
Method 2) Use decgen.
Method 3) Use deKorator.
Starting from scratch is time consuming and in the end, having a window decoration all done in code is quick and nice, but is it all worth it for one type of design?
Decgen takes an existing KWin engine, transforms the engine for your use, and allows the designer to import images directly into the engine for use. I enjoy this because I am a perpetual tweaker, I'm always going to adjust something in code, but I'll never invest the time it takes to make one window decoration all in code.
deKorator takes decgen's premise, or idea, even further, and allows the designer to use the images he supplies the deKorator engine as the window decoration. More of the manner in which things from the Windows or even Mac world do things with things like guikit. More torwards theming I think would be reasonable.
So all in all, there just three different levels - coders should stay at method 1, tweakers and hackers at method 2, and graphics artists at method 3. IMHO of course - open to debate.
Really nice update, colorizing is a good thing, but it would be even better if it followed what had in been set in kcontrol->apperance&settings->colors. Now I just most get some spare time and start making window decs=). There is no chance that you will release the David Lanham-window dec seen in the third screenshot?
Ratings & Comments
77 Comments
Is this project dead? I've downloaded the DecGen script, but cannot download the png2qrgb script. Any update on the status of this?
Very good scripts, thank you. You make the theming work far more easy and fast.
when I ported over an old windows theme with decgen 0.5, I noticed often (not always) the images were displayed in a blueish hue, instead of the original colour. what causes this?
Can you create transparent themes with this?
Does anyone else notice that this guy has a HUGE desktop? I mean, I'm running 1900x1200, and I'm pretty sure he's bigger. Where do you find a monitor to support that?
1600x1200 is the res of the screen shots.
hi, doing a ../../automerge.sh ../../images/super.h on a current kubuntu I get: industrie13@Cylonix:~/Speicher/Programme/decgen-0.5/cylonminimal-0.1/kwin$ ../../automerge.sh ../../images/super.h -en Found a valid super.h file (../../images/super.h). ../../automerge.sh: 37: let: not found head: ../../images/super.h: ungültige Anzahl von Zeilen ../../automerge.sh: 39: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found test: 51: 26: unexpected operator ../../automerge.sh: 51: let: not found -en Created tiles.h. All done. without the super.h merged into tiles.h, any ideas?
Hi, where did you find that font in the first picture?
Hello there, Alphacube decoration, which is generated with DecGen has a wrong FSF address in its Alphacube.[cpp,h] files. Could you please fix that? Also the config widget isn't working at least in here, but seems to work in your screenshots, so it might have been fixed... Just wanted to inform you about these. Thanks.
great window dec.. Whice kde style u use,,, i like it........
yes it does look slick, is it the one u were working on? anyway i hope u release it some day...
It's tiblit, I hit a 3.0 branch but it's still under very heavy development. http://www.den-4.com
I really like the dlanham type windec!
Right on, I'm a huge fan of his work...
Really like the idea of DecGen and have been using it. Various people have asked for additional buttons. Is there a way to add additional buttons to those included in the images folder? Thanks for your help in advance...
Absolutely possible, but the engine is only setup to support the standard buttons. I'd like to add support, but I've got other F/OSS projects higher priorities right now. And I'm just squeaking out a 0.5 build tonight.
doesn't decgen support amd64? the cool Alphacube style doesn't compile on my gentoo amd64 system... http://www.kde-look.org/content/show.php?content=32099
thanx for telling what's wrong :D
Anyone using 0.4 generated trees, I'm interested to see if you've got any issues when logging out of KDE and back in. Specifically, do the color settings get reset? Example, I've got a tree I added colorizing to, and I default to using KDE's color settings even when I selected the theme's colors.
Same thing here. It is corrected easily by applying the color theme again in kcontrol. I haven't thought to mention it because I never reboot.
Same problem here. Always picks up the system colours, regardless of the settings... http://kde-look.org/content/show.php?content=32099
I ask this question with all due respect to both authors, but what exactly is the difference / advantages / disadvantages and or functionality difference between the two utilities ? I ask this, just in case I'm missing something, I'm going to install decgen and give it a whirl with some of the decos I have produced for deKorator,
The main difference is that decgen is a set of tools allowing you to make a native window decoration, it transforms the images into code. The reason I prefer this is that settings such as button placement, spacing, caption height, app-icon placement, and many other things can be edited easily. Another reason I prefer decgen is that the packages are put together neatly and you don't have to keep track of image directories. I don't mean to say that deKorator isn't a good tool, just pointing out some of the benefits of decgen.
Well, I think currently we've got three processes for making window decoration, and that's 2+ over what we had last time, so progress is good. Method 1) Start from scratch (or a tutorial like http://www.usermode.org/docs/kwintheme.html) Method 2) Use decgen. Method 3) Use deKorator. Starting from scratch is time consuming and in the end, having a window decoration all done in code is quick and nice, but is it all worth it for one type of design? Decgen takes an existing KWin engine, transforms the engine for your use, and allows the designer to import images directly into the engine for use. I enjoy this because I am a perpetual tweaker, I'm always going to adjust something in code, but I'll never invest the time it takes to make one window decoration all in code. deKorator takes decgen's premise, or idea, even further, and allows the designer to use the images he supplies the deKorator engine as the window decoration. More of the manner in which things from the Windows or even Mac world do things with things like guikit. More torwards theming I think would be reasonable. So all in all, there just three different levels - coders should stay at method 1, tweakers and hackers at method 2, and graphics artists at method 3. IMHO of course - open to debate.
Really nice update, colorizing is a good thing, but it would be even better if it followed what had in been set in kcontrol->apperance&settings->colors. Now I just most get some spare time and start making window decs=). There is no chance that you will release the David Lanham-window dec seen in the third screenshot?