Quoting Bradley T Hughes <[EMAIL PROTECTED]>:I thought so... 8x8 or 16x16 (possibly configurable?) checkers in the same style as interlacing (i.e. one box is slightly darker than the other). Would make a sexy background :)
I'd say configurable. No idea what fonts people are going to use, so you can't have a one size fits all. How about:
window.title.backgroundSpread: 8
If we call it something generic like "backgroundSpread" we may decide to use it for other textures too, such as interlaced.
indeed... when the time comes to add such a thing, we can figure out the appropriate name... personally, i would go for something having "width" or "size" in the name, so that it's clear without reading the documentation what it is for.
[snip]
Idea: separator height = font height - 2 (or 4) pixels. The font for the menu frame, of course.
This is too tall for my tastes... it looks more like a [nop] with a solid line through it. But that's just me :)
[snip]Taking into account the various suggestions, I see something like this:
I favor backgroundColor and backgroundColorTo instead of color1 and color2, respectively. I think it's more suggestive to immediately show that they regard the background.
For gradients and interlaced solids, I like "color1" and "color2"; for solids, I prefer "color". The "background" seems kind of implicit to me:
menu.title.color: babyshitgreen ! the color of the menu title is ...
When I first toyed with the idea of font shadows (actually have a patch for 0.65 around here) I considered this: don't specifically request shadowedText; instead, see if any of textShadowColor or textLightColor are present in the resources. If textShadowColor is
present, do the shadow, if textLightColor is present to the light, if
one is missing don't do that one.
this is possible, except that you could use the shadowColor for things other than text...
But the only problem I saw here is how to tackle defaults. The way Blackbox works, if I got it right, if a resource is missing it will
be assigned a default value. There's never been a case IIRC where a
missing resource means it must be kept missing. This would be a first
and probably unwanted break with tradition. So perhaps using "shadow"
and "light" keywords in the appearance may be better.
Why "shadow" and "light" and not "shadowText" and "lightText"? Because we have appearance for buttons too... and perhaps we can
apply the double/triple rendering trick to button pixmaps too, in
which case we'd need a more generic keyword.
exactly... I like "shadowColor" and "embossColor"
Warning: from what I've seen during my experiments with shadowed text, some care must be taken about the window label height. I had to
add a pixel to the bottom and one at the top, because otherwise when
the label is raised/sunken, the shadow/light would touch the edges
and look ugly.
this is something that could be done when loading the style, to make sure that enough space is given for the entire text.
So let's overview the proposed changes and additions once more, see what you think:
[snip]
-- Bradley T. Hughes - bhughes at trolltech.com Trolltech AS - Waldemar Thranes gt. 98 N-0175 Oslo, Norway
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
List archives: http://asgardsrealm.net/lurker/splash/index.html
