Updating the Player extensionWe provide a free double-clickable updater to convert earlier versions of Player into version 1.1. Here's what to do:
- double click on the updater and follow the prompt to select Player (which is probably in the Extensions folder of your System Folder)
- after the updater has finished, backup the old copy of Player (e.g. on a floppy or in a compressed archive)
- drag the old Player to the trash
- empty the trash
If the updater doesn't recognize your copy of Player or Runtime as valid, try updating the original copy that you received when you purchased the product.
Updating the Player Runtime extensionTo update Runtime on a user machine (that does not have Player installed), follow the instructions above but using the Runtime updater. Runtime does not have to be in the System Folder for you to update it. (You should not have both Player and Runtime in the System Folder at the same time. That may cause a crash.)
Updating your scripts
- All of your scripts should work with no modifications.
- If any of your scripts use "locateFile" or "locateFolder", you can improve performance by modifying them to call the new "set dialog folder" verb. See the Release Notes and User's Guide for details.
AppleScript & Frontier
- As noted elsewhere, there is only one "PreFab Player"; it works with both AppleScript and Frontier. Only the supporting files and example scripts differ.
- As noted above, please delete old copies of Player. AppleScript occasionally launches the wrong version of an app (including from the trash!); deleting the old one obviously prevents that.
- If you have the Scriptable Finder (free with System 7.5) and modify your scripts to call "set dialog folder" as noted above, you no longer need PlayerLib. Although it doesn't do any harm in the Scripting Additions folder, you might want to remove it just to keep things tidy.
- The "app menu" Scripting Addition probably isn't required anymore. Nearly all modern apps respond to: tell application "name of app" to activate. app menu is no longer placed in the Scripting Additions folder during installation and is not used in any example scripts.
- As with any installation, we recommend first backing up your "Frontier.root" file. Then, run the "Install Frontier support" script and follow the prompts. In general, you will want to overwrite the existing tables to take advantage of new features.
Copyright 1993-99, PreFab Software, Inc. All Rights Reserved.
This site built and maintained using Stage Three, a set of custom Frontier scripts.