Soliant Consulting : Clients - Success Story

1 2 3 4 5 6

Architect a language layer allowing data-driven localization and external application code.

All application-layer language—field labels, user interface text, dialog text, etc.—is stored in the Language.fp7 file. No text objects were used in the solution: instead it is all driven from fields related externally. If an end-user chooses a different language for the installer (or modifies his or her existing language file), all user interface elements change appropriately.

An exploration of the language file reveals that there are three basic techniques used. First all strings that can be referenced as fields are organized into tables and global fields. These are used for layouts, text in alert dialogs, calculated fields, etc. Second, all end user value lists are stored in the language file and referenced by the main application file. Third, any script step that has options that cannot be specified by a fieldare "wrapped" in scripts within the language file and called from the mainapplication file. The best example of this is button text in "Show Custom Dialog", this text must be hard coded, so the language file contains several scripts that handle these types of dialogs. Parameter passing makes this technique quite flexible.

When this feature is used to localize a FileMaker application, you can instantly change the interface language simply by renaming one of the localized language files. For example, with FileMaker Donations, open the FileMaker Applications folder and drill down to "FileMaker Donations/Resources/Language", here you will see several localized language files, fmd_French.fp7, fmd_German.fp7, and fmd_English. If you copy and rename any of those files as "fmd_Language.fp7", and then restart Donations, the entire interface appears in the new language. In addition, if you wish to localize any FileMaker application into a language that is not yet available, you can simply duplicate the language file, open it, and enter the translated strings into the provided fields, scripts, and value lists.

Deliver complete email functionality including forms, templates, and archiving.

FileMaker Recruiter allows users to track interactions with individual contacts or groups, including all email. Rather than embed SMTP and POP capabilities in the solution, the system relies on an end-user's email client. All email is archived, and dynamic templates are provided to allow mail-merge capabilities within FileMaker Recruiter itself.

The FileMaker Applications email function makes good use of the new syntax for the Substitute function. All tags are stored as global text in the language file, and all templates are stored with user data. When it comes time to merge live data into the templates, the Substitute function neatly matches any localized tags with live data from the database.

1 2 3 4 5 6

FileMaker Recruiter 2.0

	Home \| Services \| Training \| Clients \| Resources \| About Us \| Jobs \| Site Map Copyright © 2004-2008 Soliant Consulting, Inc. All Rights Reserved.