Developer’s Guide
Table Of Contents
- Preface Introducing FileMaker Developer 5.5
- Chapter 1 Installing FileMaker Developer 5.5
- What you need to install FileMakerDeveloper
- System requirements for FileMaker Developer 5.5
- Networking requirements
- Web publishing requirements
- Requirements for advanced features (Windows)
- Requirements for advanced features (MacOS)
- Installing FileMaker Developer 5.5 in Windows
- Installing FileMaker Developer 5.5 in the MacOS
- New features in FileMaker Pro
- FileMaker Pro 5.5 and Mac OS X
- Contents of the FileMaker Developer 5.5 folder
- Contents of the Developer Extras folder on the FileMaker Developer 5.5 CD
- Read Me file
- Electronic documentation
- Abiding by the license agreement
- Registration and customer support
- About the TechInfo database
- Chapter 2 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 yoursolution
- Converting and upgrading solution files
- Chapter 3 Creating custom layout themes
- Chapter 4 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 Scriptsmenus
- Adding the FileMakerPro extension to database filenames
- Saving your settings in the Developer Tool
- Chapter 5 Distributing FileMakerPro runtime database solutions
- Chapter 6 Publishing your database on the Web
- Types of web publishing
- Using the FileMakerPro 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 networkconnection
- Opening password-protected databasesremotely
- 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 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
- 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 9 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 10 Understanding external function plug-ins
- About external functions
- About the plug-in example file
- Installing, enabling, and configuring the exampleplug-in
- Description of the FMExample plug-in’s externalfunctions
- Using the example plug-in
- Customizing the plug-in example
- 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
- Registering your plug-ins
- Appendix A Feature comparison of the runtime application and FileMakerPro
- Appendix B Valid names used in CGI requests for FileMakerProXMLdata
- 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 FileMakerPro values for error codes
- Index
Creating a database solution 2-13
Mac OS-only characters:
1 ≠ (not equal)
1 ≥ (greater than or equal to)
1 ≤ (less than or equal to)
1 √ (square root/check mark)
Designing text layouts for cross-platform solutions
Keep the following tips in mind when designing a text layout that
will display in both Windows and the Mac OS.
1 Leave plenty of room around a text block.
Even when FileMaker Pro is able to match fonts, there can be subtle
differences in character width and line spacing when fonts are
substituted on another platform. FileMaker Pro supports fixed text
object sizes, so that you can resize a text object to be longer than the
text within it. This allows you to anticipate changes in font size.
Resize your text objects so they are a little wider than the default size
to prevent text from wrapping to a second line when a different font
is substituted.
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.
Make sure fields and text objects are large enough to accommodate substituted fonts
Text bounding box
too narrow
Text bounding box too
narrow and shallow
The dotted colors are
available on 16-color
systems
This palette indicates which
colors map to black or white