So you’re submitting a proposal to present at the FileMaker Developer Conference (aka DevCon)… awesome! Thanks for offering to share your knowledge with the developer community. The more developers share, the better DevCon for us all. As you may be aware, the deadline for submitting proposals for next year’s DevCon is almost upon us.

One requirement is a 3- to 5-minute video of yourself for each of your proposed topics. The purpose of the video is to give the FileMaker, Inc. speaker selection team an idea of your presentation style, as well as to provide a platform for you to explain the key objectives of your proposed session and how you intend to present it. Although your proposal will not be judged on the video’s technical merits, you naturally will want to present yourself in the best possible manner.

Following are some suggestions on how to record and produce a quality video for this purpose… 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… »