This web site and the coding standards presented herein are for developers using the Claris/FileMaker Pro platform from Claris International, Inc. They are maintained and documented by a core group of contributors familiar with developing software applications using the software. ISO Productions, Inc. (producer of ISO FileMaker Magazine) is the official sponsor of this wiki by providing the funding for keeping the site operational.
Getting Started:
There are two primary aspects covered on this site. The first is a Coding Style Guideline and the second is Best Practices. The information provided is being cultivated in order to facilitate "clean reading" and well functioning solutions. Please note this site is not attempting to promote a solution "framework". While we do provide a starter file, the use of the documented best practices is obviously voluntary to the extent which it will benefit anyone who is able to reference the documentation maintained on this site.
Disclaimer: These are not official standards from Claris International, Inc. (read the Background section for more info).
If you're looking for information about why these standards were created then read the Background.
Otherwise, you're probably looking for the Coding Standards
The Best Practices section of this site outlines methods, systems and "ways of doing things" related to Claris/FileMaker development. As opposed to the Coding Standards, where the expectation would be following the standards as closely as possible, the Best Practices can serve as learning material or as documentation for their use and implementation.
The standards on these pages are managed and monitored by a core group of FileMaker developers who have a wide variety of FileMaker development experiences. Pages on this wiki are updated with new/revised content on a periodic basis.
Before asking for an account
Before granting a write access account, we need to verify that you're not here just to say how much "better" your method of development is. Our goal is to operate as a unified collective in pursuit of furthering these standards to the benefit of those who chose adopted them.
"Seriously my way is better!"
This site is not a place for heated debate (although debates will happen) about who's method of development is better or the best. As FileMaker developers we've all had (or still have) our "own ways" of doing things. In fact, FileMaker development is rife with individual "development standards". To join our group, a degree of ego must be left at the door in order to realize the benefits of adopting such standards.
There's a dedicated section on this wiki where all proposals are added first. This includes proposals to the Coding Standards and Best Practices areas.
Any accepted proposal will be refined through community discussion and then moved into its respective section. View the proposals area for more information.
This site was originally created using software called Confluence and the main/original contributors were Matt Petrowsky, Jeremy Bante, Perren Smith, Arnold Kegebein, Daniel Smith, Josh Ormond, Matt Navarre, Todd Geist and various others.
These standards were first documented in 2010 - 2015 and the original content has been preserved in this archived version of the older site.