Going Global
So far, the most popular posts I’ve written (if you discount the rant about syncing my mobile phone on Windows) are the two about getting dynamically loaded JavaScript code to execute in the global context.
So far, the most popular posts I’ve written (if you discount the rant about syncing my mobile phone on Windows) are the two about getting dynamically loaded JavaScript code to execute in the global context.
One of the official goals for my DOM Bindings framework (think Cocoa Bindings for the DOM), is to make Web applications as close to first class citizens as possible on your desktop. That means supporting both drag & drop and cut & paste.
I installed the latest Beta of Internet Explorer on my work laptop yesterday. In part, I was hoping to find out whether the last two applications I built which embed an Internet Explorer browser as the user interface (which is a great way to build an application’s UI quickly) would work for our customers that upgrade their browser. Unfortunately, I never did find out.
In his recent post, Wil Shipley lays down the gauntlet and bets Bill Gates $10,000 that Microsoft will be unable to ship Windows Vista on time (AKA January, which is actually much later than it was originally scheduled to ship).
How I’d love to see Gates take up this challenge. Of course, it would be best if Shipley won.
If you write lots of JavaScript — and boy, do I write a bit of JavaScript — you might be interested in a nice little unit testing library I’ve put together. There are several other JavaScript unit testing libraries out there, but they all assume you want to execute your scripts in a browser. For gnarly library code, like my implementation of Apple’s Cocoa Bindings for the DOM, running from the command line is much more conducive to integration into a real development process.