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-7
Valid values for theme attributes
The following table describes the attribute values supported by
FileMaker Pro in a layout theme. Values must be enclosed within
quotation marks (“ ”) —if a quotation mark is missing,
FileMaker Pro is unable to parse the XML and cannot display the
theme in the New Layout/Report assistant.
THEMEDEFAULT VALUE
Syntax example:
<THEMEDEFAULT VALUE=“CURRENT”/>
For more information, see “Specifying default values
for themes” on page 5-9.
VERSION VALUE
Syntax example:
<VERSION VALUE=“ver. 1.0”/>
The VERSION element is currently not used by
FileMaker Pro, but may be used in future versions.
These single-line
elements Must contain these attributes This attribute
Is used to describe these
characteristics
And may contain
these values
COLOR RGB color hex values for
background fills, text, and
borders in layout parts, fields,
text blocks, and field labels.
To display a color, the
PATTERN attribute must not
be set to “1” (which is
transparent).
FileMaker Pro themes use
web-safe palette colors to
ensure the color will appear
the same on all computers.
See “Finding values for
patterns and colors” on
page 5-9.
COLOR = “#FFFFFF”
COLOR = “#33FF00”
COLOR = “#CC9966”
Or any 6-digit hex value (a
combination of numbers 0-
9 or letters A-F) preceded
by the # symbol.
EFFECT Embossing, engraving, or
drop shadow 3-D effects for a
field, text, or field label.
When used in conjunction
with a field border, the line
width of the effect will be the
same as the border pen size.
The pen size value must be
greater than zero in order for
the effect or border to appear.
VALUE = “EMBOSS”
VALUE = “ENGRAVE”
VALUE =
“DROPSHADOW”
VALUE = “NONE”
FONT The name of the font. More
than one font name can be
specified, separated by
commas. The first font
available on a user’s
computer will be used in the
layout.
Note Font values are case
sensitive and must be entered
in sentence style with initial
caps only.
FONT = “Times New
Roman”
FONT = “Geneva”
FONT = “New York,
Times, Helvetica, Arial”
Or any other available font
(In FileMaker Pro, choose
Format menu > Font to see
the available fonts.)