This is just a heads up that PopBox 2.0 should be coming out in the next couple of days. It is feature complete and I am just doing some compatibility and regression testing prior to calling it done. The documentation is almost finished as well, so barring something unforeseen 2.0 should be out by Friday.

It's much easier to use and the most requested features are all in there. Here's a list of enhancements:

• Allows for a different image to be used for the thumbnail and Popped image, with built in preload, caching and wait images.
• No longer need to add the call to Revert to your image tag. It will be called automatically.
• Added PopBar transparency, which allows you to overlay text on the thumbnail image also.
• Allows you to display the RevertBar and PopBar above the image or overlaid on the image.

When I released PopBox a couple of weeks ago the community received it very well and it looks like I may have been able to help out a lot of people. That's great and in part what it's all about.

I did however receive a request for the same feature over and over, and that was for a small "X" or close box in the upper right hand corner of the Popped image to make it obvious to the user how to close it.

I resisted this feature request for days, thinking that no user could truly not figure out how to close an image. It seemed simple enough to me - you click it to open, you click it to close. Since PopBox also has the ability to automatically close the image when the mouse cursor leaves the image I figured I had all the bases covered.

Besides - adding the close box to the upper right corner of the image would be hard.

But the request kept coming in. So I did what any smart man in my position would do: I asked someone smarter - my wife.

Gentlemen, you should all be as lucky as I to have the wife I have. Only go find your own of course. She said to me, "So you don't want to do it because it would be hard?" That pretty much ended the conversation.

Not to be outdone I decided to make my close box the fanciest, most functional, slickest and classy close box I'd ever seen. It's a multi-element transparency with text and an image that really allows you to direct the user as well as being intuitive.

My wife's comment? "You think you're pretty fancy, doncha!" That's all I need.

You can check it out at the PopBox product page, and I've finished the documentation page as well.

Do you have a web site? Do you display small images that represent larger ones such as "thumbnails"? Or do you need to dynamically move or resize images on the page? Then you need PopBox!

With only a few simple modifications to your web page your thumbnail images will be "popping" out of the screen when visitors click on them instead of reloading a time-consuming second page.

PopBox is an image magnification javascript solution for dynamically resizing your images on your web page, with only 3 simple lines of HTML/Javascript code. And it's free!

I've written up an introductory article on PopBox, or you can go straight to the product page now!

The planned network upgrade went very smoothly today and the web site was down for only a couple of hours from about Noon to 2:00.

My average speeds are now:

• Download Speed: 9466 kbps (1183.3 KB/sec transfer rate)
• Upload Speed: 10994 kbps (1374.3 KB/sec transfer rate)

I know that's not a big deal for most businesses with T1s and such, but for running my server from home over fiber DSL that's great!

Product release tomorrow...

Due to a planned network upgrade the web site may be down for a couple of hours on Wednesday, May 23 in the afternoon PST. I don't have an exact time or length of outage but I'm excited about the prospect of much faster speeds.

I'm also still on track to release my product on Thursday, so remember to check back!

My current internet provider here in CA is SureWest, and I personally haven't had any problems with them. In fact, they have been very easy to work with and have even upgraded my speed once or twice without a price increase which is always nice. Well, they're doing it again.

On May 23 they have scheduled me to get a fiber drop and a bandwidth increase to 1MBps synchronous. The fact that this is a synchronous connection means that my upload speed will be the same as my download speed, which makes a big difference when you run an internet-facing server on my side of the connection. Late next week you should notice a big difference in page responsiveness.

The only downside that I can see is that they tell me I will need a new IP address and could be down for up to 4 hours, so I've decided to delay my product launch until the day after the upgrade so as to avoid any outages so close after launch. I don't really expect a flood of visitors to be trying to get through but I do expect the product to become popular (and not just because it's free) and I'd rather not look flaky.

So if you have a lot of images or screen shots on your web pages be sure to check back on May 24!

I've been sidetracked for the last couple of weeks with a completely different product, but I got excited about it and totally went for it. I finished it this morning but I can't release it until the web docs and product page are complete so I'm working on that. It sure takes a long time to produce anything on only an hour or two a day.

I won't get super specific on what it is right now, but I will say that it's a great little javascript library product that will greatly enhance any web page that displays images. Did I mention it's free?

I should be able to release it early next week and then I can get back to my commercial product.

On the Business of Software site we had a discussion of e-commerce providers where we talked about the good and bad of creating your own e-commerce system vs. going with an established 3rd party provider. I thought it would help if there was a comparison matrix that would allow you to see the costs before you made a choice, since it's difficult to decide between a provider who offers 1.9% + $0.21 per transaction or one who offers 2.1% + $0.19 per transaction.

The numbers obviously depend on lot on your product price, but I've just made it all easy to calculate for you with this handy matrix. It's changed my mind!

My fiber router went down today taking me offline for about an hour. Someone was, a-hem, checking some telecom lines with a multimeter and accidentally sent a little shock through pins 1-2 of the RJ45 interface cabling.

I didn't notice the outage until I tried to access the internet about a half hour later. I got lucky that rebooting the router solved the problem and I've promised myself NOT to touch those lines again. Traffic to my site is on the rise but it's still pretty low, so it's a silver lining that probably few people noticed. :)

Over the course of the last month or so there has been a lot of talk on the blogs about recursion. It's being touted as a great way to separate the good programmers from those who don't know what they're doing, but I think in the middle of all the praise it should be noted that despite the benefits of recursion it has a nasty downside: Recursion doesn't scale.

I suppose that somewhere in the heart of the mass of cubes it settles down to a dull hum, but here on the edge traffic is considerable. Just a few days ago a cube mover was pushing a squeaky-wheeled cart down the aisle and the pitch of the wheel squeak was like fingernails on a chalkboard. I had to cover my ears and hum while I had flashbacks of Eddie Murphy plugging his ears and yelling "I'm not listening to you!"

I've already received email about my rss feed showing duplicates. I know - it's a pain but I really needed to make my feed standards compliant if I was going to continue doing this. It's better to do it now than a year from now when there would be a lot more entries. If it's really really bothersome you can delete the feed and re-add it. Sorry for the inconvenience.

I also noticed that compression was wreaking havoc with my SSL-enabled pages. Response time was literally in the minutes instead of seconds. That obviously won't work for e-commerce. Either the FlatCompression filter can't correctly compress a https stream or my lamo server CPU can't handle the load of compressing and encrypting. It's a pretty old server so I'm betting on that. I was able to add FlatCompression headers to keep from compressing those pages and the problem was solved. Since I can't afford a new server any time soon I'll have to structure my e-commerce/shopping cart pages to be under a different directory or subdomain so I can easily add these headers in IIS.