Developer’s Guide
Table Of Contents
- Chapter 1 Getting started
- Chapter 2 Using FileMaker Developer features
- Chapter 3 Using the Developer Utilities
- Overview of preparing your solution files
- Modifying database solution files
- Considerations for a runtime database solution
- Binding databases into runtime database solutions
- Saving and reusing Developer Utilities settings
- Converting and upgrading solution files
- Removing full access privileges from databases
- Chapter 4 Distributing runtime database solutions
- Chapter 5 Customizing database solutions
- Chapter 6 Creating custom layout themes
- Chapter 7 Developing third-party FileMaker plug-ins
- About external functions
- About the example plug-in
- Installing, enabling, and configuring the example plug-in
- Description of the FMExample plug-in’s external functions
- Using the example plug-in
- Customizing the plug-in example
- Requirements for writing external function plug-ins
- FileMaker messages sent to the plug-in
- Avoiding potential Mac OS X resource conflicts
- Providing documentation for your plug-in
- Registering your plug-in
- Appendix A Feature comparison of the runtime application with FileMaker Pro
- Index
Creating custom layout themes 51
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 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, such as title text in the header.
XML elements and their theme attributes
The following tables describe the multi-line and single-line XML
elements supported by FileMaker
Developer in a layout theme
document. Unknown elements are ignored by FileMaker
Developer.
Table of multi-line elements
<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.
<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.
FMTHEME
(required)
VERSION
THEMENAME (required)
THEMEDEFAULT
Any or all layout part elements