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 49
Follow the instruction in the New Layout/Report assistant. The third
panel presents you with a list of themes to select from.
If your new themes don’t appear in the New Layout/Report assistant,
you might have made a syntax error. For information, see
“Checking
theme files for errors” on page 56.
Requirements for theme files
FileMaker Developer layout themes are described in an XML
document saved in text file format. Each text file must have the .fth
filename extension and reside in the Themes folder inside the
FileMaker
Developer application folder.
XML resembles HTML in many ways. However, unlike HTML the
XML for layout themes must be well-formed and comply with the
required syntax. Omitting a required element or attribute, or
mismatching start and end tags will result in an unusable document
and FileMaker
Developer will be unable to parse the XML or display
the theme in the New Layout/Report assistant.
Minimum XML elements for themes
Every theme file must begin with an XML-document processing
instruction that declares it as an XML document using the XML
1.0
specification. In addition, an XML document for a layout theme
must contain the <FMTHEMES> and </FMTHEMES> start and end
tags for the file. This FMTHEMES root element can contain one or
more FMTHEME element.
Containing all of your themes (FMTHEME elements) in one file is
useful if you want to organize the way that themes appear in the New
Report/Layout assistant. The order that FMTHEME elements are
listed in the file determines the order in which the THEMENAME
values appear.
Note Values for the THEMENAME element can contain any
characters from the ASCII character set. However, if you’re using an
XML editor to write your themes or if you plan to use the themes on
different platforms, certain measures must be taken.
Names of custom themes appear as options in the New Layout/Report assistant
Minimum elements required for a theme file