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
7-10
Developer’s Guide
The following is an example of an –edit request for editing records
in a portal, where “Address::” is the name of the relationship,
“City.1” is the first row in the portal, and “City.2” is the second row
in the portal:
FMPro?–db=employees.fp5&–lay=LayoutOne&recid=11&
FirstName=Sam&LastName=Smith&Address::City.1=Seattle
&Address::City.2=New York&–format= –fmp_xml&–edit
The following is an example of another –edit request for editing
records in a portal, in an HTML form:
<FORM ACTION="fmpro" METHOD="POST">
<INPUT TYPE="HIDDEN" NAME="-db" VALUE="employees.fp5">
<INPUT TYPE="HIDDEN" NAME="-lay" VALUE="LayoutOne">
<INPUT TYPE="HIDDEN" NAME="-format" VALUE="-fmp_xml">
<INPUT TYPE="HIDDEN" NAME="-recid" VALUE="11">
<INPUT TYPE="TEXT" NAME="FirstName" VALUE="Joe">
<INPUT TYPE="TEXT" NAME="LastName" VALUE="Smith">
<INPUT TYPE="TEXT" NAME="Address::City.1" VALUE="San
Jose">
<INPUT TYPE="TEXT" NAME="Address::City.2" VALUE="Santa
Clara">
<INPUT TYPE="SUBMIT" NAME="-edit" VALUE="Edit Record">
</FORM>
Using style sheets with your
XML document
The Web Companion will generate an XML-stylesheet processing
instruction with each grammar if the FileMaker CGI request includes
the –styletype and –stylehref parameters. This allows you to use
cascading style sheets (CSS) or Extensible Stylesheet Language
(XSL) documents for displaying your XML document.
The –styletype parameter is used for setting the value of the type
attribute (type=text/css or type=text/xsl).
The –stylehref parameter is used for setting the value of the HREF
attribute (href=document.css or href=document.xsl).
Here is an example of what a possible FileMaker CGI command
might look like:
http://localhost/fmpro?–db=employees.fp5&–format= –fmp_xml&–find=&
–styletype=text/xsl&–stylehref=document.xsl
Based on this command, the Web Companion will include the
following processing instruction in the XML document:
<?xml-stylesheet type=“text/xsl” href=“document.xsl”?>
The following text is an example of a possible XSL document used
with the FMPXMLRESULT grammar. In this example, the XSL
document converts the XML document into an HTML document by
inserting HTML tags. It builds an HTML table that contains a header
row for all the field names from the METADATA element in the
FMPXMLRESULT grammar, and table rows for all the field data in
the ROW elements of the RESULTSET.
Note This is an example of XSLT that was written to work with
Internet Explorer 5.0 for Windows, not with other browsers using
later versions of XSLT.
<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl"
xmlns:HTML="http://www.w3.org/Profiles/XHTML-transitional">
<xsl:template>
<xsl:apply-templates/>
</xsl:template>
<xsl:template match="text()">
<xsl:value-of/>