Developer’s Guide
Table Of Contents
- Chapter 1 Welcome to FileMaker Developer
- Chapter 2 Installing FileMaker Developer in Windows
- Chapter 3 Installing FileMaker Developer in the Mac OS
- Chapter 4 Creating a database solution
- Overview of preparing your solutionfiles
- Considerations for a runtime databasesolution
- Considerations for Kiosk mode
- Using scripts to control your solution
- Protecting your database solution files
- Providing user documentation
- 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
- Your responsibilities as a developer
- Testing before and after creating your solution
- Converting and upgrading solution files
- Chapter 5 Creating custom layout themes
- Chapter 6 Using the FileMaker Developer Tool
- About the solution examples
- Using the FileMaker Developer Tool
- Binding your databases into a runtime database solution
- Creating Kiosk-mode solutions
- Renaming your databases
- Removing design access to your databases
- Customizing the About, Help, and Scripts menus
- Adding the FileMaker Pro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 7 Distributing FileMaker Pro runtime database solutions
- Chapter 8 Publishing your database on the Web
- Types of web publishing
- Using the FileMaker Pro Web Companion
- Creating a custom home page
- Creating a custom home page for Instant Web Publishing
- Creating a custom web site using a database layout
- Web Companion support for Internet mediatypes
- Monitoring your site
- Exporting data to a static HTML page
- Testing your site without a network connection
- Opening password-protected databases remotely
- Chapter 9 Custom web publishing using CDML
- About the CDML examples
- General steps for custom web publishing using CDML
- About CDML format files
- Generating FileMaker Pro CGI requests using CDML
- Using the CDML Tool and templates
- About the CDML Reference database
- Creating error messages
- Using an encoding parameter with a CDML replacement tag
- Planning your web site
- Chapter 10 Using FileMaker Pro XML to deliver your data on the Web
- About the XML examples
- General process for custom web publishing using XML
- Generating an XML document
- Using the FMPDSORESULT grammar
- Using the FileMaker Pro Extended XML grammars
- About UTF-8 encoded data
- Generating FileMaker Pro CGI requests for an XML document
- Using style sheets with your XML document
- Comparing CSS, XSLT, and JavaScript
- Looking at the XML Inventory example
- Chapter 11 Using JDBC to deliver your data
- About the JDBC examples
- About JDBC
- Using the FileMaker JDBC Driver
- SQL supported by the FileMaker JDBC Driver
- FileMaker Pro support for Unicode characters
- About the FileMaker JDBC Driver interfaces and extensions
- Example 1: Looking at the FileMaker Pro Explorer application
- Example 2: Creating the JBuilder Inventory application
- Example 3: Creating the Visual Cafe Inventory application
- Chapter 12 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing an external function plug-in
- FileMaker Pro messages sent to the plug-in
- Debugging your plug-in
- Avoiding potential Mac OS resourceconflicts
- Providing documentation for your plug-in
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMaker Pro
- Appendix B Valid names used in CGI requests for FileMaker Pro 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
- Generating a -dup request
- Generating an -img 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
Creating a database solution 4-13
If you put a left-aligned label over a column of right-aligned
numbers, for example, the report might look fine on your computer.
But font substitution could cause field labels to shift when the file is
opened on another computer. If a wider font is substituted on the
second computer, your column heading will shift to the right. If a
more narrow font is used, the text will display too far to the left.
• Avoid mixing text and fields because character spacing may vary.
If necessary, use merge fields—for example, to place a field in the
middle of a sentence.
Using a common color palette
When 256 or more colors are available, FileMaker Pro will offer an
88-color palette that is virtually identical across platforms. (Close
substitutes are used for 13 colors that do not match exactly.)
Windows computers using a standard VGA driver will only display
16 colors. Some older Mac OS computers may also be limited to 16
colors. The 16-color palette in FileMaker Pro varies slightly between
Windows and the Mac OS, depending on the Windows color scheme
you are using.
If you are building your files on a 256-color computer, you might
want to use colors that will map well to 16-color systems. It also
helps to know which colors map to black and which map to white for
monochrome displays.
The dotted colors are This palette indicates which
systems
available on 16-color colors map to black or white
Using graphics in cross-platform solutions
If you’re storing and displaying graphics across platforms, be sure to
select the document preference for Store compatible graphics before
importing each graphic into your database file:
Choose Edit menu > Preferences > Document.
Mac OS X: choose FileMaker Developer application menu >
Preferences > Document.
Two copies of the graphic image will be stored: the original version
(for example, bitmap, metafile, or GIF) and one in PICT file format.
Graphics with gradients that are imported and stored as bitmaps will
redraw faster on the screen than graphics imported and stored as
PICT images. Additionally, PICT images containing gradients may
have some quality degradation when displayed on Windows
machines.
If your graphic image has an undesirable white border surrounding
an irregularly shaped graphic, you should create a mask for the
bitmap image. Refer to the documentation that came with your
graphics program for more information.
Using QuickTime movies in cross-platform solutions
To use a Mac OS QuickTime movie with FileMaker Pro for
Windows, first save the movie in a format playable on non Apple
computers using a QuickTime editing application. For more
information, visit the Apple web site at www.apple.com.
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.