Developer’s Guide (Mac OS)
Table Of Contents
- Chapter 1: Welcome to FileMaker Pro SDK
- Chapter 2: Installing FileMaker Pro SDK
- Chapter 3: Preparing solution files
- Chapter 4: Binding solution files
- Chapter 5: Distributing your bundled solution
- Appendix A: FileMaker Pro Runtime features
- Appendix B: SDK file locations
- Index
Chapter 3: Preparing solution files
This chapter describes how to prepare your solution files before binding. It
covers what to do after you’ve developed a solution and includes tips for
developing a solution using KioskMaker. It also describes how to convert
an existing FileMaker Pro 2.x SDK solution file to a FileMaker Pro 3.0
SDK solution.
Note This guide assumes you’re familiar with FileMaker Pro and have
developed database solutions. For specific explanations of the
FileMaker Pro application functionality, refer to the user’s guide that
comes with the FileMaker Pro 3.0 application.
Preparing a solution—an overview
In preparing your solution files, you should implement the following:
1 an “About” layout to introduce your solution
1 a customized Help system
1 scripts/buttons to open and close auxiliary files
1 passwords to protect your solution
Here are some suggestions for the general steps to follow in preparing
your solution files:
1. In FileMaker Pro 3.0, design the files that make up your solution.
If you’re developing a solution that runs on both Macintosh and
Windows, make sure you follow all platform-specific rules, such as
naming conventions. See the Cross Platform Tips (XPLATTIP on
Windows) file in the Support folder for information. If you’re
converting solution files from FileMaker Pro 2.x, see “Converting
and upgrading solution files” on page 3-12 for information.
2. Add an “About” layout.
You should name your layout “About <solution name>.” You can
include your name, address, and technical support phone number on
the layout—you are responsible for providing technical support for
your bundled solution. If you don’t provide that information in the
“About” layout, make sure it appears in your supporting
documentation. See “Creating an “About” layout” on page 3-4 for
design tips.