I'll be doing some blog maintenance in the next few days.
The code highlighter blows, so I'm replacing it with one that can also be used in the comments. That means I have to go through all 75+ posts and change the code to display the VBA properly 
And I'm upgrading to WordPress 2.6.2.
So the blog might be down periodically. When I'm updating, you might get a "back in 15 minutes" sign.
Apologies in advance.
–JP
About JP
6 Comments:
Jimmy -
What code highlighter will you be implementing? I tried a bunch when I started my blog, and settled on the one with the lowest suck factor. But I still didn't like it, so I've reverted to writing my own
This one:
http://blog.igeek.info/still-fresh/category/wp-plugins/igsyntax-hiliter/
It's the same one from DDoE. I modified it slightly so it shows "VBA" instead of "VB".
I was previously using this one: http://www.ericbess.com/ericblog/2008/03/03/wp-codebox/
This is the same one from Chandoo's blog, and it's a great highlighter, but for some reason the colors weren't working on my blog. The code in the codebox was showing as plain black-on-white text.
It still isn't ideal. If I could write my own plugin, I'd combine the best features of both (like the ability to collapse the codebox).
I was using the same one as on Daily Dose. I didn't like the colors, but never got around to changing them. But also, the indentation was unreliable, and the whole thing just didn't feel right.
When I get around to it, I'll change the colors so they're more like the VBIDE.
igsyntax doesn't work well in comments, imo. You still have to manually escape the less-than character or it will interpret it as an html tag. Oh, you can put a note to commenters to do that, but they won't. The next commenter on ddoe that does it will be the first.
How wonderful. Well, I don't get much code in the comments anyway. I'm more concerned about my own posts having the syntax coloring.
Thx,
JP