Developer’s Guide
Table Of Contents
- Chapter 1: Installing FileMaker Pro Developer Edi...
- Chapter 2: Binding solution files
- The binding process—an overview
- Before binding
- Binder and runtime terminology
- Specifying the primary file
- Naming the runtime solution
- Assigning the binding key
- Choosing auxiliary files
- Choosing binding options
- Assigning the three-character extension
- Specifying a location for solution files
- What happens during binding
- Binding cross-platform solutions
- Changing solutions
- Chapter 3: Preparing and managing runtime soluti...
- Chapter 4: Distributing your bundled solution
- Appendix A: Feature comparison—runtime Appendix ...
- Appendix B: About the TechInfo database
- Index
iv
FileMaker Pro Developer’s Guide
Permanently remove access to Define Fields, Define
Relationships, ScriptMaker, and Access Privileges
2-9
Disable runtime solution closing splash screen
2-10
Use custom “About” script
2-10
Use custom Help script
2-12
Rename Script menu
2-13
Assigning the three-character extension
2-14
Assigning the extension in Windows
2-15
Assigning the extension in the Mac OS
2-16
Changing extensions for cross-platform compatibility
2-17
Specifying a location for solution files
2-17
What happens during binding
2-19
Binding cross-platform solutions
2-20
Changing solutions
2-20
Chapter 3: Preparing and managing runtime solutions
Preparing a solution—an overview
3-1
Considerations before binding
3-2
Documenting your files
3-4
Protecting your solution files
3-5
Policy on decoding and repairing passwords
3-6
Developer responsibilities
3-6
Testing your solution
3-7
Design tips for cross-platform solutions
3-8
Fonts
3-8
Font styles
3-9
Character sets
3-9
Color palettes
3-10
Graphics
3-11
Layout tips
3-11
Moving files between platforms
3-12
Showing the status bar in Windows 95
3-13
Printing tips
3-14
QuickTime movies
3-14
Creating cross-platform scripts
3-15
About the Status (CurrentPlatform) function
3-15
Converting and upgrading solution files
3-16
Converting solution files
3-16
Importing to a new solution file
3-16