Download v1.3 (September 29, 2018)
Mac OS 10.12 minimum
This application displays HyperCard stacks in Mac OS X.
The binary format of HyperCard stacks has been retro-engineered by numerous people, and now it is known with pretty good reliability. If you want to learn more about it, see the format description.
HyperCardPreview only displays the stacks, it does not edit them, it does not execute them. To do that you have to use a emulator: SheepShaver, Basilisk or vMac. Or try stacks in the HyperCard Stack Archive. Or install SuperCard, a HyperCard clone still maintained today.
It makes the seeing the stacks an experience of the old days. The look is very close to the original one, with bitmap fonts, old-style scrollers, aliasing. In the Home stacks the look is accurate to the pixel, as in most Apple stacks, but less so if there are colors, and not at all if there are XCMDs.
- very accurate display,
- declares the stacks as its own files, so they have an icon again in the Finder,
- can open stacks from both HyperCard v 2.x and v 1.x,
- can open stacks with private access by hacking the encryption.
- can export texts, images and sounds.
How to use it
Browse with Keyboard
Change Card: press an arrow key, or page up / page down / home / end
Show/Hide All Cards: press enter or return
Browse with Trackpad
Change Card: scroll left or right, or swipe
Show/Hide All Cards: pinch
Display Button/Field Info
Get Button Info: press command-option (like in HyperCard), buttons are colored in blue and you can click on one to display the info.
Get Field Info: press command-option-shift (like in HyperCard), both fields and buttons are colored in blue and you can click on one to display the info.
Get Info of a Covered Button or Field: right-click somewhere on the card, the list of the buttons and fields at that location appears, from the frontmost to the outmost. That way you can get info about a button or field even if it is covered by the others.
The format of the JSON file is here.
Some sounds can't be read: they beep instead of play, and they can't be exported. That's because HyperCardPreview can't read compressed sound resources, only uncompressed ones.
Colors of the AddColor XCMD are technically handled but cause troubles. For example the stack "Color Tools" is not good at all because the display is managed partly by scripts, which are not executed. Besides, macintosh pictures (
PICT resources, which have a complex format designed by Apple) are still accepted by Mac OS X but with restrictions, especially there is no transparency.
Stacks of HyperCard 1.xx are handled but not accurarely displayed. The problem is that HyperCard changed some display settings between versions 1.xx and 2.xx, for example the text field margins, and HyperCardPreview doesn't handle that. In fact, HyperCardPreview displays v1.xx stacks as if they were just converted to v2.xx and were displayed the v2.xx way.
HyperCardPreview doesn't display other scripts that HyperTalk.
It doesn't execute any script or any XCMD or XFNC.
HyperCardPreview doesn't use any deprecated API, so its future is bright.
That means that old APIs had to be partially re-coded: resource fork reading, resource management, text display, bitmap fonts, 1-bit imaging.
It seems that I can't have a developer ID without paying a fee to Apple. And I'm not ready to do it just for that little soft.
Changes since version 1.0
Changes in v1.3
The whole structure of a stack can be exported to a JSON file.
Images of cards and backgrounds can be exported.
The resources of a stack can be inspected and exported (icons, pictures, sounds and the rest).
Changes in v1.2
The application is now signed.
Bug fixes in the card list.
Changes in v1.1
Now the scroll fields can be scrolled, and the pop-up buttons can be popped up.
The tools to explore the stacks have been added, it is far more convenient.
Glitches corrected in stacks:
- vector fonts are now well displayed,
- AddColor is (nearly) handled,
- stacks with private access can be opened
…plus a lot of other little bug fixes and optimizations.
Unfortunately, the QuickLook plug-in had to be removed because it is not handled in Swift. A Swift plug-in may work but just if it is the only one plug-in in Swift in the OS, elsewhere it crashes the QuickLook platform, so it is risky.
The future of the app
It won’t grow much larger than that.
I don’t intend it to edit stacks and execute scripts, it would make an app several times more complex, and as long as nobody is using the stacks anymore, I don’t see the point.
But if you have bugs with some of your stacks, please inform me.
Can HyperCard be ported to Mac OS X?
If you have that in mind, check Stacksmith.
In my opinion, HyperCard might be re-invented, but with a big restriction on the use cases. HyperCard had too many of them and that’s why it was so difficult to explain when people asked what it did. For example, HyperCard had cards and backgrounds, intended for display of content (text, images, databases), which is now perfectly handled by websites.