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
Creating custom layout themes
5-9
Specifying default values for themes
FileMaker Pro uses default values to replace attributes that are
invalid or missing. For each theme listed in a theme file, you can
specify whether the default values are determined by the current
layout settings (which change when a user changes them) or by
standard layout values (the same values that FileMaker Pro uses
when creating a file for the first time).
<THEMEDEFAULT VALUE=”CURRENT”/>
<THEMEDEFAULT VALUE=”STANDARD”/>
If you don’t specify a value for the THEMEDEFAULT element in
the theme, FileMaker Pro will use standard layout values by default.
Finding values for patterns and colors
The values for the patterns in the FileMaker Pro pattern palette are
numbered consecutively—starting with the top row and counting
from left to right, where the value for the top left pattern in the palette
is 1, the value for the next pattern to the right is 2, and so on. Five
patterns in the first row can also be defined with words: NONE (= 1),
SOLID (= 2), DKGRAY (= 6), GRAY (= 7), and LTGRAY (= 8).
Note The first pattern (value = 1) is transparent and the second
pattern (value = 2) is solid. For objects with a color fill, be sure to use
the solid pattern.
STYLE Character styles for text in
fields, text blocks, and field
labels. More than one style
can be specified, separated by
commas or spaces.
No error checking is done for
contradicting styles, such as
UPPERCASE and
LOWERCASE.
The PLAIN style value
overrides all other style
values.
STRIKEOUT and
STRIKETHRU values are the
same.
STYLE = “PLAIN”
STYLE = “BOLD”
STYLE = “ITALIC”
STYLE = “STRIKEOUT”
STYLE =
“STRIKETHRU”
STYLE = “SMALLCAPS”
STYLE = “UNDERLINE”
STYLE =
“WORDUNDERLINE”
STYLE =
“DBLUNDERLINE”
STYLE = “UPPERCASE”
STYLE = “LOWERCASE”
STYLE = “TITLECASE”
STYLE =
“SUPERSCRIPT”
STYLE = “SUBSCRIPT”
STYLE = “CONDENSE”
STYLE = “EXTEND”
STYLE = “ITALIC,
BOLD, SMALLCAPS”
This attribute
Is used to describe these
characteristics
And may contain
these values
Pattern attribute values begin at the top left corner
of the fill pattern palette with number 1 and end at
the bottom right corner with number 64
2 3 4 5 6 7 81
57 58 59 60 61 62 63 64