AppleScript: The Missing Manual

Appendix B. Moving from HyperCard to AppleScript

Back in the days before DVDs, iPods, and take-out sushi, everyday Mac fans used HyperCard to write simple automation programs. Sure, HyperCard couldn’t command other programs, but its simplicity and power made HyperCard a favorite tool for thousands of budding programmers.

In addition, HyperCard was one of the first programming tools to let people build their program’s interface through drag-and-drop—more than a decade before Interface Builder came along. HyperTalk, the programming language for HyperCard, was highly regarded for its English-like syntax and shallow learning curve. And even hard-core programmers respected HyperCard stacks (interfaces bundled with code) for their small file size.

Unfortunately, Apple stopped supporting HyperCard soon before releasing Mac OS X. If you happen to be one of the Mac fans who depends on HyperCard for everyday work, therefore, you’re left with only a few choices:

• Continue using HyperCard in Mac OS X’s Classic mode. Classic is Apple’s buzzword to describe Mac OS 9 programs running in Mac OS X. Unfortunately, since HyperCard wasn’t designed for Mac OS X, using HyperCard in Classic is likely to result in a major slowdown of your code. Plus, you’ll continue to see HyperCard’s old, gray, Mac OS 9-style windows—a scourge on the attractive interface of Mac OS X.

• Buy a Mac OS X program that can open HyperCard stacks. Such programs include SuperCard ($180, www.supercard.us) and Revolution ($150-$900 depending ...