Reddit [Note: this review was greatly improved thanks to corrections and insights from Kevin Calhoun, HyperCard 2. HyperCard was what chiefly convinced me to buy my first Mac; I still regard it as the neatest, most useful, most generous program ever conceived. Generous because it was originally given away free no more, alas! If you love the Mac, you should worship Bill Atkinson. Anyhow, I do. Meanwhile Atkinson had been working on HyperCard then called WildCard , built around four elements: buttons to push text fields to type into or click on screens "cards" containing buttons and text fields plus graphics the capacity to set up automatic "links" to take you from one card to another This fourth element, still residually present e.
|Published (Last):||23 May 2004|
|PDF File Size:||19.41 Mb|
|ePub File Size:||3.92 Mb|
|Price:||Free* [*Free Regsitration Required]|
Reddit [Note: this review was greatly improved thanks to corrections and insights from Kevin Calhoun, HyperCard 2. HyperCard was what chiefly convinced me to buy my first Mac; I still regard it as the neatest, most useful, most generous program ever conceived. Generous because it was originally given away free no more, alas!
If you love the Mac, you should worship Bill Atkinson. Anyhow, I do. Meanwhile Atkinson had been working on HyperCard then called WildCard , built around four elements: buttons to push text fields to type into or click on screens "cards" containing buttons and text fields plus graphics the capacity to set up automatic "links" to take you from one card to another This fourth element, still residually present e.
Besides letting you calculate, manipulate variables, loop and test, and do all the other things you expect from a programming language, HyperTalk includes system messages reporting user actions, commands to simulate them, and functions and "properties" to obtain and alter the state of the interface and the machine.
You acquire a stack someone else has written: you look inside it, see what makes it tick, modify it. But according to legend, HyperCard spirit has not been universally understood at Apple. There are stories of Chris Espinosa and John Sculley having to push for its original release. Perhaps there was resistance to the idea of giving away for free an application that essentially let users write their own applications; certainly there was enough fear that the idea of "programming" would repel users that Apple gave it the euphemistic name "scripting.
After 2. Happily, HyperCard has survived to become 2. Improvements and Enhancements — Version 2. Sorting and finding are more powerful; date format conversion is better; doMenu can take modifier keys; and "there is" can check for disks, applications, documents, and card pictures. There is better menuItem info, more convenient reference syntax. WorldScript is supported. At last you can determine the layering order of fields and buttons via a new property, "the partNumber. More major changes make it easier to conform to the Mac Thought Police style.
Radio buttons now automatically work in sets. Buttons can be disabled, and can be in standard Mac style. Simple pop-up buttons are now a standard feature, with an interesting by-product that a button can now be a container. Fields can more easily act like scrolling lists. Objects can be double-clicked. Finally, a stack can now be saved as an application!
QuickTime — HyperCard 2. The Movie XCMD puts up a movie window, in any of several styles, with or without a controller; you can manipulate the movie from a handler, or let the user do it with the controller. Many features of the movie can be manipulated, with a number of valuable messages and a callback feature. A utility stack installs the XCMD for you and simplifies setting up a movie window.
Color — HyperCard 2. Integrated color was a much hoped-for feature that Claris was reportedly working on for its abortive 2. Now 2. You can color buttons and fields and add colored rectangular areas to cards; select or create the object, and click on a color.
Each object has a solid color and can have a beveled edge of adjustable thickness. You can also display full color PICTs as part of the card. You dictate the layering order of the color items, and you can use over 25 transition effects as you apply color.
The utility stack installs the XCMD, and modifies your handlers and gives your stack a database of permanently colored objects, so that color automatically appears. Color seems part of the card: moving the card or switching stacks presents no problems or major delay unlike earlier third-party colorizers.
You can also control the XCMD yourself, so that color objects can change in interesting ways as part of a handler: a button could suddenly become colored, a rectangular region of the card could change colors with a transition effect, and so on. I have seen this system criticized on the nets as a kludge, but I find it ingenious.
However, I was at first overwhelmed by the spectacular appearance of the Color Tools stack, and thought, "Wow, colored buttons and fields look like this?!? HyperCard has long been a leader here; even before MultiFinder, you could use HyperCard to launch another application, and return when it quit. Basic support for Apple events arrived in 2. Now, however, HyperCard accepts some different events, operating on 17 kinds of objects and their properties; it is thus scriptable, and you can control HyperCard from AppleScript or any other Apple event-sending mechanism.
A statement in a script, or a multiple statements in a container, can be sent into the system in any of these languages via the "do" command. If the language is QuicKeys, which is not message-oriented, you can launch it with a new "run" message. If the language is AppleScript, messages can be passed directly between it and HyperTalk. Much of the value of this new power lies in the future. Bugs and Shortcomings — Apple fixed some bugs and serious misbehaviours, including the infamous "go first marked card" bug.
Documentation — The documentation manuals and some stacks is good, but not uniformly so. HyperCard is hard to describe or teach, and though the manuals do a remarkably fine job of both at describing and teaching and the included stacks are superb as models, the manuals have errors, ranging from simple misprints and misstated syntax rules to howlers like a demo script for a Replace function that breaks if the replace-text contains the find-text.
There are also odd arrangement choices and some serious omissions. Properties of palettes and external windows are not included in the Properties chapter. The Choose message is not documented in the manuals; nor is the important new "run" message.
Many basic arrow-key navigation shortcuts are documented only deep in a Help stack. The "dynamic path" is incorrectly explained in the HT Reference stack. The new "copy template" command is practically undocumented. Such shortcomings in the official documentation seem somewhat outrageous. Email Address.
Each card contains a set of interactive objects, including text fields, check boxes, buttons, and similar common graphical user interface GUI elements. Users browse the stack by navigating from card to card, using built-in navigation features, a powerful search mechanism, or through user-created scripts. They place GUI objects on the cards using an interactive layout engine based on a simple drag-and-drop interface. This way, a stack of cards with a common layout and functionality can be created. The database features of the HyperCard system are based on the storage of the state of all of the objects on the cards in the physical file representing the stack. The database does not exist as a separate system within the HyperCard stack; no database engine or similar construct exists. Instead, the state of any object in the system is considered to be live and editable at any time.
HyperCard 2.2: The Great Becomes Greater
He earned a B. I would think Runrev would as well, as they ought to understand how beneficial this would be, especially to new users. Comments and reviews What are comments? I realize that the GUI has changed and a lot has been added in about 20 years. I taught myself Hypercard using the first hypercrad of this book without access to a Mac!