My main development machine is a MacBook Pro so to maintain support for Internet Explorer I rebooted my machine into XP, updated the development environment, built, and then tested. This would take about 45 minutes so I often wouldn't do it before checking in new features of Ogoglio and inevitably I wouldn't take into account some quirk of Windows and IE support then would break.
This last week I decided to stomp out all of the remaining IE bugs in the Ogoglio viewer and I started by booting XP in Parallels Desktop and fixing all of the browser test pages. Much to my surprise, all of the new browser tests pass, including the Java3D initialization, but when I tried to open the ogoglio viewer it failed.
To make a long story short, I poked around and found that we could make Java3D boot on machines with low-end graphics cards which can't antialias or double-buffer. Now Parallels renders Ogoglio (badly) and I can debug WinIE against my OS X development kit. It isn't pretty, but it beats rebooting.
Comments