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
5-4
Developer’s Guide
Removing elements from a theme file
The FileMaker Pro layout theme files contain multi-line elements for
fields, field labels, text, and every part in a layout. Each of these
elements contains other multi-line elements and single-line
elements. You can remove any of these elements, but you must
remove the entire element—that is, everything inside the element’s
start and end tags and the start and end tags as well.
FileMaker Pro will use default values for any elements you remove
(see “Specifying default values for themes” on page 5-9).
A single-line element, such as the PEN element, begins with <PEN
and ends with /> on a single line, and looks like this:
<PEN COLOR="#000066" PATTERN="2" SIZE="0" />
A multi-line element has start and end tags that look like this:
<BORDER>
</BORDER>
To remove a multi-line element, delete the start and end tags and all
elements contained within them. For example, to remove a multi-line
BORDER element in the Blue_gold.fth file, delete all three lines:
<BORDER>
<PEN COLOR="#000000" PATTERN="2" SIZE="1" />
</BORDER>
XML elements for layout parts
An FMTHEME element can contain any of the following multi-line
elements to describe the parts in a FileMaker Pro layout. Each layout
part element contains additional elements to describe the background
fill, text, field labels, and fields in the layout part.
Elements for layout parts can be listed in any order within an
FMTHEME element in the XML document. However, if two
identical elements are listed (such as two BODYPART elements),
FileMaker Pro will only use the attributes for the last one in the list.
This multi-lined
element is used To describe this layout part
<TITLEHEADERPART>
</TITLEHEADERPART>
Title header — appears only once at the top
of the first screen or page.
<HEADERPART>
</HEADERPART>
Header — appears at the top of every screen
or page (except the first one if there’s a title
header).
<LEADGRANDSUMPART>
</LEADGRANDSUMPART>
Leading grand summary — appears at the
beginning of a report and displays a
summary field for all the records in a found
set. (A layout can have only one leading
grand summary part.)
<LEADSUBSUMPART>
</LEADSUBSUMPART>
Leading subsummary — appears above the
body part and displays a summary field for a
subset of records as defined by the break
field. You can describe up to nine leading
subsummary layout parts — each
LEADSUBSUMPART element must
contain a PARTNUMBER element to
distinguish it from the others.
<BODYPART>
</BODYPART>
Body — appears in the middle of every
screen or page. (A layout can have only one
body part.)
<TRAILSUBSUMPART>
</TRAILSUBSUMPART>
Trailing subsummary — appears below the
body part and displays a summary field for a
subset of records as defined by the break
field. You can describe up to nine trailing
subsummary layout parts — each
TRAILSUBSUMPART element must
contain a PARTNUMBER element to
distinguish it from the others.