- Web Viewer apps can be created like regular web applications:
- Files don’t need to be concatenated together.
- Files can be created and edited in an external text editor and imported into FileMaker.
- Web Viewer apps can be run and debugged in your browser of choice.
- FilerMaker data is supplied to the web app separately.
- Scripts can easily be called from a web viewer.
- Data can be sent to a web viewer from a FileMaker action.
- A web viewer can request data from FileMaker and then handle the response via a callback function, similar to a true Ajax request.
- Data retrieval is fast. One example in the sample file is a 400,000 character book which is retrieved in 200 ms.
- Installation is as simple and modular as possible:
- Three tables and a few relationships.
- One necessary layout.
- Added tables don’t need to be related to your project tables.
- Added scripts shouldn’t need any configuration.
For a refresher about the practices leading to this module, see my last post.
As web viewers become more than a portal to external websites, and instead become a way to use local web code, it gets trickier to keep everything organized and working properly. We’ve done the legwork of discovering as many pitfalls as possible, and this module is the result of that. If you have a very simple web app, you may not feel that you need much organization, but it may be wise to get organized with it now in case you’d like to expand in the future.
We’ve hosted FMAjax in a GitHub repository, so please download it there. If you have any issues, please add them to the Issues tracker there.
UPDATE: for those of you who attended my talk at Apple or DigFM or beezwax on Nov 12-13, you can download the demo file here. Login credentials are username: Admin, password: admin.