Patric Rhone had a link to this article over at Tom's Hardware that was quite informative. The linked page is kind of in the middle of the article, so click around to read all of it. The basic conclusion is one that I've been aware of for quite a while: Apple hardware is not overpriced, but their upgrades are. As long as you're willing to go to NewEgg or FirstTech to get your RAM and hard drives, there's no price-related reason not to buy Apple hardware. It seems a little ironic to me that the people who could legitimately complain about Apple's prices (for upgrades) are the people who can't install their own RAM. That's not, to my recollection, the people who complain about the cost of Apple hardware.

Facebook | Twitter | Reddit | Stumble

As a Mac user in a windows shop, I feel I need to use Mac applications when I can rather than the sometimes better open source alternatives to Microsoft products. I use Firefox because I find it to have two or three critical improvements over Safari, but Safari is getting there. I use iChat for instant messaging and I use Mail for all my email. iChat has its issues, but that's another post. This one's all about Mail.

During the average business day, I receive a multitude of email messages of varying priority. I found that it would be useful to be able to mark priority by color. Many email clients have this ability including Thunderbird, so I felt a little left out by Apple on this one. Searching the Internet, I found details on how to set up filters that will automatically change the color of an incoming email, but that's childsplay. I also found AppleScripts to manually change the color, which seemed like too much of a hack to me.

As it turns out, this functionality is built into Mail.app and, while it's not as user-friendly as a right-click option, it works quite well. Here's how to do it.

• Select the message you wish to change to a different color
• From the Format menu, select Show Colors. ( Shift-Cmd-C )
• Choose your favorite color-picker. I like the crayons
• Choose a color for the message.

It may not look like this did anything right away so choose another message and experience the beauty of your new colors. If you do this a lot during the day, just leave the color picker open so you have quick access to it. You'll need to re-open the color picker the next time you start Mail.app.

Happy coloring!

Facebook | Twitter | Reddit | Stumble

I don't know if it's useful to anyone but me, but I was trying to figure out the best way to display a random image on a webpage. What I ran into for using Server Side Includes is that the image to show is defined in my css which isn't parsed by the server for includes and apparently include directives within class= statements are ignored with my server configuration.

Well, it seemed that there should be a simple way to do this. The result was to create a configuration-less perl script that displays a random image from the folder it's in. It currently only does files that end in .jpg, so I'll leave that change as an exercise for the reader.

If you just want to use the script, here are some instructions. In the directory where your source images are stick the code in a file whatever name you like as long as it ends with .cgi or .pl, I'd suggest something like randomimage.pl. Make the file executable (chmod a+x randomimage.pl (windows users are on their own)). In your html or css use the name of your file as the name of the image, something like "http://www.yourdomain.com/randomimages/randomimage.pl" would work nicely. This will work best if all the images are the same size so the web page doesn't look different every time and you can define the image dimensions in the html or css.

#!/usr/bin/perl

opendir (THISDIR, "./") or die "no such directory: $!";
@imagelist = grep { /.*\.jpg/ } readdir THISDIR;
closedir (THISDIR);

$max = $#imagelist + 1;

$imagenumber= int(rand($max)) ;

print "Content-type: image/jpeg\n\n";

open (IMAGEFILE, "<", "./$imagelist[$imagenumber]") or die "can't open file $imagelist[$imagenumber]";
foreach (readline (IMAGEFILE)) {
    print;
    }
close (IMAGEFILE);

Anyway. No guarantees. No promises. Code provided as is and free for any legal, non-malicious use.

--Ben

Facebook | Twitter | Reddit | Stumble

This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.
This blog post is all about obfuscation.This blog post is all about obfuscation.

Facebook | Twitter | Reddit | Stumble

Looks like I need to add a "Computers" section to my news page here... Done.

So, I use iChat on a fairly regular basis at work. It's great for getting a slightly quicker response to questions. (He says as he waits for a response to a question.) But I discovered an interesting problem and figured that I wasn't alone for once.

When I open up a new chat using the iChat menu-bar icon, I get a second, identical window directly behind the first. Not a big deal. I just close the second window and go on with my chat. It started to get a little annoying though. After a couple of quick googles, I found a forum thread over at Apple that dealt with the issue. They suggested deleting the com.apple.ichat.plist preference file which I had deleted earlier for a different reason. They also suggested deleting the com.apple.iChatAgent.plist which I haven't tried.

Anyway. I found one possible solution. If you're having the same problem, check out this thread at Apple.

Facebook | Twitter | Reddit | Stumble