Note: This page has fallen into abeyance; work on FaceSpan 5 has ceased. However, I’ve left this information here, as it might be useful to those interested. Just be aware that facts and links may be out of date and that I have no intention of updating them.

FaceSpan 5

What was FaceSpan 5?

First of all, what was FaceSpan? Similar to HyperCard, FaceSpan was a software construction kit; it emerged at the same time as AppleScript, about 1991, and AppleScript was its programming language. As originally conceived, it was elegant and easy to use, a great way for AppleScript programmers to create a user interface for their scripts. It was bought by DTI in 1996. When Mac OS X came out, DTI first let FaceSpan languish, then rewrote it on top of Apple’s own AppleScript Studio, so that it lost most of its virtues and acquired a lot of AppleScript Studio’s faults.

Then in 2005, Mark Alldritt / Late Night Software, for whom I had done some documentation and programming work, bought FaceSpan and started to rewrite it from the ground up again as FaceSpan 5. The idea was to bring back the elegance and simplicity of the HyperCard-type model, where every interface object has its own script, messages are passed automatically up the containership chain, and every object can see every other object and its script. Plus, since Mark also wrote Script Debugger, FaceSpan 5 would have debugging built in. This turned out to be a massive task, but at the time I first wrote this page it was coming along and the results were pretty astounding. I was helping out with documentation and other forms of alpha tester support.

• Mark kept a blog about FaceSpan 5 developments.

• I helped write this description of what FaceSpan 5 was all about.

• I thought were really getting somewhere when I was able to write a useful application using FaceSpan 5.

• Unfortunately, work on this project was ultimately abandoned. This is a real pity because what Mark had created was a truly great programming environment. In a single integrated development environment, you could design your application’s interface, give code to various application objects, and run and debug the application; it’s like REALbasic or HyperCard. The resulting application is a Cocoa application, but much easier than Xcode, a portion of Cocoa pared down and simplified and given a much better programming and design interface. The trouble was, though, that AppleScript had been chosen as the user programming language, and these days Apple just doesn’t understand AppleScript any more, so that Mark couldn’t accomplish what he wanted to because Cocoa Scripting wouldn’t let him catch and parse the various Apple events the way he needed to.

Back to main page

This page prepared March 30, 2026 by Matt Neuburg, phd = matt at tidbits dot com, using RubyFrontier. RubyFrontier is a port, written in the Ruby language, of the Web-site-creation features of UserLand Frontier. Works just like Frontier, but written in Ruby!
Download RubyFrontier from GitHub.