Web technologies have added functionality to FileMaker solutions since the Web Viewer layout object was introduced in version 8.5. The web viewer has proven especially useful for displaying Flash-generated charts from FusionCharts, Maani, AnyChart, and others.

FileMaker Pro v11 introduced a built-in chart layout object with 5 basic chart types. Charts suddenly became much easier to implement in FileMaker Pro!

However, with FileMaker Go for iPad and Phone (separate apps) built-in charting is not supported and Apple’s iOS doesn’t run Adobe Flash. The Google Charts API is popular, but for that you must be online.

Luckily, the potential of HTML5 for charting is huge, and the spec that affects charting functions (via the canvas tag) is fairly stable. Read more… »

This workshop provides hands-on opportunity to apply suggested tactics for embracing the new user interface. Whether you think it boon or bane, incorporating the modernized Status Toolbar (formerly Status Area) requires new thinking about layout design and user interaction options. Its re-location and newly available buttons and features change the rules, especially when upgrading existing solutions or in cross-version deployments.
Read more… »

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… »

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… »