Ok so I recently thought I should do a Qtcurve window decoration theme to temporarily replace the Aurorae theme used for windows (just to simplify life for everyone wanting to try it out and provide some unification of the work). So I open the .qtcurve file and start doing edits but quickly realize that beyond some simply fixes I can't figure out what it is can be done and can't be done...

I quickly, obviously, google for "qtcurve documentation" but strike out completely.

So what I need to do is take a weekend, sit down with the qtcurve file and simply test my way around. Change one thing, document the change and then go onward that way. Then I could write out a quick "how to" for qtcurve so everyone can play around with it properly and we can all make our mock-ups into reality.
BUT - the issue is, its a massive document with tons of different settings - so it would rock if we all could join up and try to figure out what it does together? To help out future design-aficionados with it?

What do you guys and girls think?

I was thinking of something along the lines of the "conky" and "tint2" documentation available... something that we could post as a resource for designers.

Have you tried using the inbuilt editor in qtcurve? Seems pretty straightforward, although it too could do with a visual refresh. Just wondering whether it's worth writing the instruction manual to use the in-built editor, rather than editing the text files? Or maybe you could reference both?

Out of interest have you seen these theme engine: http://kde-look.org/content/show.php/Qu ... ent=101088 (on github here: https://github.com/DexterMagnific/QSvgStyle). Seems pretty interesting although development is stalled due to lack of interest.

Yeah I was more interested in the actual text document... which for some reason seems more pleasant to me or at least as if it had more options. At least thats my sensation when trying wildly to configure it and keep striking out in that the options aren't that nice.

@ jenns
Although off topic, I wanted to know if you had ever tried, BE::Shell, that Qt interface is very flexible, and maybe you could take a cue for something with the next Qt widget style from the technical point of view
http://sourceforge.net/p/be-shell/wiki/Installation/
https://www.google.it/search?q=be::shel ... 80&bih=914