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-12
Developer’s Guide
1 Check the alignment of the field labels and their associated
fields—they should both be aligned in the same direction.
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.
1 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.
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.) 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.
The dotted colors are available
on 16-color systems
This palette indicates which
colors map to black or white