Developer’s Guide
Table Of Contents
- Contents
- Chapter 1 Introducing FileMaker Developer 5
- Chapter 2 Customizing your database solution
- About the custom solution examples
- Using the FileMaker Developer Tool
- Binding your databases into a runtime database solution
- Displaying databases in Kiosk mode
- Renaming your databases
- Removing design access to your databases
- Customizing the About, Help, and Scriptsmenus
- Adding the FileMakerPro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 3 Preparing files for a custom solution
- About the Relational Example
- General steps for preparing your solutionfiles
- Issues to consider before creating a runtime database solution
- Opening files in Kiosk mode
- Design tips for navigating in Kiosk mode
- Creating startup scripts
- Using button image samples
- Documenting your database solution
- Design tips for cross-platform solutions
- Creating a consistent appearance
- Simulating outline and shadow text styles
- Using common character sets
- Designing text layouts for cross-platform solutions
- Using a common color palette
- Using graphics in cross-platform solutions
- Using QuickTime movies in cross-platform solutions
- Showing the status bar in Windows
- Using separate scripts for printing
- Using the Status (CurrentPlatform) function
- Creating platform-specific scripts
- Protecting your runtime database solutionfiles
- Testing before and after creating yoursolution
- Converting and upgrading solution files
- Chapter 4 Distributing FileMakerPro runtime database solutions
- Chapter 5 Creating custom layout themes
- Chapter 6 Publishing your database on the Web
- Moving forward using open web standards
- Using the FileMakerPro Web Companion
- Displaying a custom home page
- Using a custom home page with Instant Web Publishing
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a networkconnection
- Opening password-protected databasesremotely
- Using the Web Security Database
- Chapter 7 Using FileMakerPro XML to deliver your data
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMakerPro Extended XMLgrammars
- About UTF-8 encoded data
- Generating FileMakerPro CGI requests for an XML document
- Using style sheets with your XMLdocument
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 8 Using Java and JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBCDriver
- FileMakerPro support for Unicodecharacters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMakerPro Explorer application
- Example 2: Creating the JBuilder Inventoryapplication
- Example 3: Creating the Visual Cafe Inventory application
- Using the FileMaker Java classes
- Chapter 9 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMakerPro CGI requests using CDML
- Using the CDML Tool and templates
- New and modified CDML tags
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 10 Writing external function plug-ins
- About the plug-in examples and templates
- Installing, enabling, and configuring FileMakerPro plug-ins
- Using external functions in a calculation
- Requirements for writing an external function plug-in
- FileMakerPro messages sent to theplugin
- Debugging your plug-in
- Avoiding potential MacOS resourceconflicts
- Providing documentation for your plug-in
- Naming and registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B Valid names used in CGI requests for FileMaker XML data
- Generating a –find, –findall, or –findany request
- Generating a –view request
- Generating a –new request
- Generating an –edit request
- Generating a –delete request
- Generating a –dbnames request
- Generating a –layoutnames request
- Generating a –scriptnames request
- Generating a –dbopen request
- Generating a –dbclose request
- Specifying parameters for the request
- db (Database)
- lay (Layout)
- format (Format)
- recid (Record ID)
- modid (Modification ID)
- lop (Logical operator)
- op (Comparison operator)
- max (Maximum records)
- skip (Skip records)
- sortfield (Sort field)
- sortorder (Sort order)
- script (Script)
- script.prefind (Script before Find)
- script.presort (Script before Sort)
- styletype (Style type)
- stylehref (Style href)
- password (Database password)
- field name (Name of specific field)
- Appendix C FileMaker Pro values for error codes
- Index
3-10
Developer’s Guide
1 What to do in case of a damaged file (see “Recovering damaged
files” on page 4-7)
1 How to reach you for technical support
You might also want to include the following recommendations:
1 Tell your users not to rename any solution files (except the runtime
application), or they may be unable to run your solution.
1 Recommend that users back up their data regularly. You might
want to automate some of the process by including scripts that save
copies of the solution files.
For more information on automating a backup procedure, see
appendix B, “Backing up and recovering files,” in the
FileMaker Pro 5 User’s Guide.
Important In the event that your runtime database solution files
become damaged, make sure users have access to your technical
support email address or telephone number in your printed
documentation or in a text file. If a database file is damaged, they
may not be able to access the About layout in your solution to find
out how to contact you.
Design tips for cross-platform solutions
If you’re developing a database solution to be run on both Windows
and Mac OS machines, there are many issues that require planning
and consideration—for example, which font technology, colors, and
design conventions to use.
Creating a consistent appearance
To ensure a consistent look for files across platforms, try to use the
same font technology, for example TrueType. It is best to use fonts
with identical names, styles, and metrics on both platforms. When
fonts used to view a file are different from the ones used to create the
file, there can be problems with word wrapping and placement.
Most font vendors supply Windows and Mac OS versions of the
same font. Contact your font vendor for more information.
When you move a file from one platform to another, if the font used
to create the file isn’t available, another font will be substituted. In
FileMaker Pro for Windows, you can specify how fonts are
substituted in the Microsoft Windows Registry Editor. You can add
more fonts to the Registry Editor to include more font substitutions.
If there is no match and no substitute is defined, FileMaker Pro
changes the font to Arial. In the Mac OS, FileMaker Pro attempts to
substitute a similar font.
Simulating outline and shadow text styles
The Windows platform doesn’t offer outline and shadow text styles.
If you want a shadow effect for titles or headings, simulate the look
by positioning two copies of a text block so that the foremost copy
appears to cast a shadow against your layout.
This Windows font Is substituted with this Mac OS font
MS Serif Times
Times New Roman Times
Times New York
Tms Rmn Times
Courier New Courier
Courier Monaco