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-5
Note Although a theme may include descriptions for every type of
layout part, the type of layout you select in the New Layout/Report
assistant determines which parts will appear in your new layout or
report.
For information about layout parts, see chapter 6, “Creating and
managing layouts and reports,” in the FileMaker Pro 5 User’s Guide
or see FileMaker Pro Help.
XML elements for text
Any layout part element can contain FIELD, TEXTLABEL, and
TEXT elements that are used to describe the characteristics of text or
data in the part.
The FIELD element is used to describe text (data) in fields and field
borders. The TEXTLABEL element is used for field label text. Field
labels are displayed in the body part of a layout or in other parts such
as the header of columnar reports. The TEXT element describes all
other text that appears in a layout part (other than fields or field
labels), such as title text in the header.
Description of XML elements and their
theme attributes
The following tables describe the multi-line and single-line XML
elements supported by FileMaker Pro in a layout theme document.
(Unknown elements are ignored by FileMaker Pro.)
Table of multi-line elements
<TRAILGRANDSUMPART>
</TRAILGRANDSUMPART>
Trailing grand summary — appears at the end
of a report and displays a summary field for all
the records in a found set. (A layout can have
only one trailing grand summary part.)
<FOOTERPART>
</FOOTERPART>
Footer — appears at the bottom of every
screen or page (except the first one if there’s
a title footer).
<TITLEFOOTPART>
</TITLEFOOTPART>
Title footer — appears only once at the
bottom of the first screen or page.
This multi-lined
element is used To describe this layout part
These multi-line
elements May contain these elements
FMTHEMES
(required)
FMTHEME
The FMTHEMES root element can contain
multiple FMTHEME elements. (The order that
they are listed determines how they’ll appear in
the New Layout/Report assistant.)
FMTHEME
(required)
VERSION
THEMENAME (required)
THEMEDEFAULT
Any or all layout part elements
TITLEHEADERPART
HEADERPART
LEADGRANDSUMPART
BODYPART
TRAILGRANDSUMPART
FOOTERPART
TITLEFOOTPART
FILL
FIELD
TEXT
TEXTLABEL
LEADSUBSUMPART
TRAILSUBSUMPART
FILL
FIELD
PARTNUMBER
TEXT
TEXTLABEL