Site Updates – Great news!

[Benjamin]

I noticed that. I'll see what I can do.

[Benjamin]

I'll go ahead and turn them off until I get a chance to look at the code and get the entities issue fixed.

[Christopher]

I am currently using "Avalon" and whatever version of the logo you have on there looks great. (I'm not biased. )

Also, when you scale the logo down, I recommend using sinc (Lanczos) as the scaling algorithm.

The logo looks it has gotten a little fuzzy. Perhaps you should sharpen it?

[RobertGonzalez]

I scaled it down in photoshop so that it was clipped at the edges. Sadly, my Illustrator skills are crap, and editing an SVG that is all over the place makes it that much more difficult.

I'd bet the "fuzz" is a combination of loss of sharpness due to scaling and the compression of the shadow at smaller resolution.

[pickle]

Email/IM me the SVG & I should be able to resize it in Illustrator.

[califdon]

I'd bet the "fuzz" is a combination of loss of sharpness due to scaling and the compression of the shadow at smaller resolution.

Nah, it's because you spilled coffee on your monitor, Robert!

[RobertGonzalez]

Done.

[Eran]

You have to increase the height of the code box and decrease the line-height. Very hard to read code this way.

[Benjamin]

You have to increase the height of the code box and decrease the line-height. Very hard to read code this way.

Can you post a screen shot please.

[Eran]

I attached a screenshot of how I see it using the subsilver2 theme (the old forum theme). I also added a screenshot of the same code-box with some CSS tweaking in Firebug (changed line-height from 1.5em to 1em, added 5px left padding and increased the height to 150px)

[Benjamin]

I'm not sure why the 1.5em line spacing had such a dramatic effect in your browser. I went ahead and removed the line-spacing completely and added a left padding of 5px.

[Benjamin]

As far as the height goes this is an issue and I'm trying to think of the best solution in order to fix it. Changing the height really isn't a valid solution because then you will have issues where you end up with white space when there isn't enough code to fill it up.

How would you guys feel about removing the Syntax: line altogether and just have the white code section? The ability to download/expand/contract/hide/show would be removed. The code area would simply be the size of the code block inside of it, which is sometimes fairly large.

[Eran]

I'm not sure why the 1.5em line spacing had such a dramatic effect in your browser

I'm not sure why you would think otherwise, line-height determines the height of each line. 1.5em means 50% bigger line height. I'm using Firefox 3.6.2 by the way. Also, it seems to be inheriting the line-height from another class (.post-body or something like that), so it's currently at 1.4em and not really a big difference from before.

As far as the height goes this is an issue and I'm trying to think of the best solution in order to fix it. Changing the height really isn't a valid solution because then you will have issues where you end up with white space when there isn't enough code to fill it up.

You can change height to max-height, that way it would fill up to the given value (at least on browsers that support that property correctly). Either way, it's too short right now

[Benjamin]

I'm not sure why the 1.5em line spacing had such a dramatic effect in your browser

I'm not sure why you would think otherwise

Because in the browsers I used to add the line-height, firefox and chrome, the spacing wasn't even remotely close to being that large. I'm on Unix however. I did not test it in Windows.

[Benjamin]

Either way, it's too short right now

You do realize there is an "Expand" function right?