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 57
1 All elements are complete. There are no missing attributes, values,
quotation marks, start tags, or end tags.
1 All values are enclosed in quotation marks (“value”). There are no
missing opening or closing quotation marks, and there are no missing
values (no blank quotation marks “ ”).
1 All elements and attributes are spelled correctly.
1 All attribute values are spelled correctly and are valid.
1 Every single-line element ends with />.
1 All multi-line elements are spelled correctly and their start and end
tags match (for example, <BODYPART> and </BODYPART>).