FREQUENTLY ASKED QUESTIONS
11. Where can I get MetaCard?If you have anonymous FTP access to the Internet, you can download the free MetaCard Starter Kit (which includes complete on-line documentation and is fully functional except that it places a limit on the length of scripts you can create for each object) from ftp://ftp.metacard.com/MetaCard/ or ftp://ftp.uu.net/vendor/MetaCard. You can also get it from the Get MetaCard page.
The distribution can also be emailed, or sent out on CDROMs or DAT tapes (a nominal charges applies for the latter two). Contact MetaCard Corporation at firstname.lastname@example.org or call 303-494-6763 if you want to get the distribution either of these ways. Be sure to specify which platform you'll be using MetaCard on if you want MetaCard emailed to you.
After installing the software, you can license it by following the
directions in the Licensing stack (available from the MetaCard Help
menu). Your initial MetaCard license includes 1 year of unlimited
technical support via email and free upgrades for 1 year. After that,
you'll need to renew a subscription as specified in
With 5 and larger packs, individuals names do not have to be supplied. A single key is supplied, and copies are made of the license Home (mchome.mc) stack. It is the responsibility of the site-support contact to ensure that no more than the licensed number of Home stacks exist on the sites machines. If more than 1 user will be using MetaCard, or if the licensed user will change frequently, a 5 or larger pack is therefore strongly recommended.
Any license can be upgraded to a larger license at any time by paying
the difference between the prices of the smaller and larger licenses.
Licensees granted the 50% educational discount who later wish to sell
applications that they have developed with MetaCard can upgrade to a
commercial license by paying the difference between the educational
and commercial price.
Subscriptions are priced yearly according to the table below, and educational institutions will receive a 50% discount from these prices. Unlimited technical support via email is available separately priced according to the table below, and the 50% discount *does not* apply to this service. All pricing is in U.S. Dollars.
Subscription Technical Support Single user 300 200 5-user 1000 300 10-user 1500 300
To upgrade, you should relicense the new Home stack rather than continue to use your old one. It's technically possible to use your old Home stack, but the color and custom properties set in that stack may conflict with the new development environment rendering it ugly at best and inoperable at worst. See the directions in the file README.install for details.
To subscribe, go to http://lists.runrev.com/mailman/listinfo/
The messages posted to the various incarnations of the metacard list are archived at http://lists.runrev.com/pipermail/metacard/, http://www.mail-archive.com/metacard%40lists.runrev.com/ and http://www.mail-archive.com/metacard%40lists.best.com/.
If you have comments or questions about the list, please address them to email@example.com.
An article on a MetaCard application for Linux appeared in the November
1997 issue of the Linux Journal. An extensive comparison of MetaCard
with Tcl/Tk and the Desktop Korn Shell (dtksh) appeared in The X
Resource Issue Eleven (Summer 1994), an O'Reilly & Associates
publication (707-829-0515). This document, titled Interactive GUI
Development Environments, is available as
Interactive GUI Development Environments.
Many of the books on HyperCard can be used to supplement the MetaCard documentation, since the scripting languages are compatible. Some examples include the 3rd Edition of Danny Goodman's best-selling "The Complete HyperCard 2.0 Handbook", Dan Winkler's "HyperTalk 2.2: The Book" and "Cooking with HyperTalk 2.0", and "HyperProgramming - Building Interactive Programs in HyperCard" by George Coulouris and Harold Thimbleby.
A contract was signed for third party book by a major publisher a
while back, but unfortunately the author missed several deadlines and
the contract was canceled.
You'll need to distribute an engine together with your stacks. You'll also need to distribute the mctools.mc stack if you use any of the standard dialogs or bitmaps (icons or cursors). You can also use the built-in "Resource Mover" to move these objects into your stack instead.
If you prefer a single-file distribution, you can use the "Standalone Builder" to bind your stack to the engine and make a single executable file.
|FAQ | Overview . Licensing . How To . Common Problems . Consultants . Testimonials|