Posts tagged “best practices”.
A Startup Subscript: Checking version/platform/device
Funny how a new platform (FileMaker Go for iPad, in this case) helps you tighten your code design. While putting together the Charting on the iPad contest starter file, naturally I rewrote the subscript that checks versions at file start to include mobile devices. For each variation it can specify minimum version and whether to enforce, allow/advise, or deny any access. The script is more modular and easily extensible by app version, OS, OS version, or device form factor. It has four parts, essentially:
1. You decide your desired behavior rules:
# Whether to advise & allow, enforce version, or deny ANY access # ( 0 or null=ignore, 1=advise but allow, 2=enforce version, # 3=deny ANY access, 4=unsupported platform but allow ) # Min version & enforcement level of FM Go for iPad Set Variable [ $minVersion_FMGo_iPad; Value:"1.0" ] Set Variable [ $enforceLevel_FMGo_iPad; Value:1 ] # # Min version & enforcement level of FM Go (for iPhone) Set Variable [ $minVersion_FMGo_iPhone; Value:"99" //will assure test fail ] Set Variable [ $enforceLevel_FMGo_iPhone; Value:4 ] etc., etc., etc.
2. Then you query the computing environment: Read more… »
Create Context-Aware Help Systems
Built-in or Bolt-on? Ideally, only the developer knows for sure. Bring your powered up laptop to this hands-on workshop and leave with a context-aware Help system integrated with one of your own FileMaker Pro solutions. The techniques presented are plug-in free and platform independent. Step-by-step you’ll develop a functioning Help system. As a bonus, you’ll also receive generic Help content for common user actions, such as finds and navigation.
Read more… »
The Art and Business of User Documentation
Producing good user documentation isn’t trivial — but it is one key deliverable that can dramatically enhance a developer’s professional image while improving the usefulness of the solution. Developers often consider solution documentation a drudgery — or worse, a time-consuming activity with little return on effort. This session convincingly explains why including documentation as a standard practice is an asset rather than a liability, and that it doesn’t need to be a huge resource drain if it is planned for and executed during the development process.
Read more… »

