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
Preparing files for a custom solution
3-13
To save a QuickTime movie in a cross-platform format:
1. On your Mac OS machine, start your QuickTime editing program.
2. Open the QuickTime movie you want to convert.
3. Choose File menu > Save As and save the file with a new name and
the .mov filename extension.
4. Select Make movie self-contained.
5. Select Make playable on non Apple computers.
The first time you play a movie from another platform,
FileMaker Pro prompts you for the location of the movie. Keep the
files in a common folder and avoid choosing the wrong file—this
could lead to unexpected results.
Showing the status bar in Windows
FileMaker Pro for Windows includes an option to show the status
bar, which allows users to specify whether status bar information at
the bottom of a window is visible or not.
If your layouts are designed to take up most of the available screen
space, users can deselect this option in FileMaker Pro or in your
runtime application to make more room.
To show the status bar:
1 Choose View menu > Status Bar.
A check mark next to the menu item indicates that the option is
selected.
Using separate scripts for printing
Scripts that include Page Setup/Print Setup and Print commands are
not 100% compatible across platforms. The print steps in the
ScriptMaker
®
feature rely upon the current printer driver in order to
determine the paper sizes that are available, page orientation, and so
on. Even if a computer using Windows and another using the
Mac OS are connected to the same printer, the drivers themselves are
significantly different—so FileMaker Pro is unable to restore page
setup and print options across platforms.
To work around this, you can do the following:
1. Create separate scripts for Windows and Mac OS. First, open the
file on your Windows machine and create the script for printing from
Windows. Then, move the database file to the Mac OS machine and
create the script for printing from the Mac OS.
2. In ScriptMaker, use the If script step and the Status
(CurrentPlatform) function in both scripts to determine whether to
run the Windows or the Mac OS script. For more information, see
“Using the Status (CurrentPlatform) function” next.
3. Make sure the Perform Without Dialog option for the Print script
step is not selected. This will allow users to change the setup options
before they print.
4. In Layout mode, choose Layouts menu > Layout Setup, select Fixed
Page Margins, and specify margins for Top, Bottom, Left, and Right.
Using the Status (CurrentPlatform) function
FileMaker Pro includes a status function that lets you determine the
platform on which the database solution is being run. This allows
you to perform different script actions such as changing to a different
layout or performing a platform-specific script step.
Status bar help