YOUSEFUL / FILEMAKER
Documentation checks
This first documentation set targets the current v1.0.0 implementation, reviewed on 2026-09-20. The registered dispatch tables, implementation and existing harness cases are the source for product behavior.
Scope
- Sixteen product guides, each with FAQs, examples, a tutorial and troubleshooting.
- Shared getting-started, FAQ, example index and tutorial index pages.
- Links from the root README and existing function references.
- Eighteen standalone sample scripts across all sixteen products, with a three-record SQL fixture, setup notes, expected results, and a ZIP containing 21 files.
Verification boundaries
| Check | Result |
|---|---|
| Product guide coverage | 16 of 16 products |
| Local links and anchors across learning pages and sample index | 156 checked; no broken targets |
| Calls in FileMaker code blocks | 111 names and argument counts checked against dispatch tables |
| Standalone sample scripts | 18 listings match the checked tutorial blocks, containing 72 plug-in calls |
| Sample archive | 21 files checked for ZIP integrity and exact agreement with source files |
| Deterministic native outputs | 42 checks passed across 11 plug-ins, including JS/Python/PHP execution |
The native checks covered text cleanup, file path and I/O results, Query result formatting with mock SQL rows, encryption round trips, barcode validation/SVG, URL helpers, MIME parsing and the language examples. They made no external network requests. Query's mock rows verify serialization and cached row access, not a live database's SQL execution.
Local checks verify links and anchors, function names and argument counts against the 378 registered functions. Native example probes use the existing mock FMWrapper harness and rebuilt plug-ins to check deterministic results. They do not parse or execute complete FileMaker script blocks.
The following still require the reader's FileMaker/test environment:
- Creating the Query sample table, committing records, and executing its actual SQL.
- Editing Script Workspace steps and displaying custom dialogs/container fields.
- Scheduler callbacks under FileMaker's real idle behavior.
- The interactive Dialog/UI tutorials and driver-dependent Print tutorial.
- HTTP/Curl requests and FTP connections to the reader's service and account.
The preceding plug-in rebrand passed 1,283 harness assertions across all sixteen products. That is implementation regression evidence, not a claim that every tutorial has been run end-to-end inside FileMaker.
Documentation conventions
Use the current Ysfl prefixes, state prerequisites, and label variable results.
Capture a plug-in error before another operation or metadata getter can clear it.
Include cleanup for sessions, temporary files and altered settings. Keep credentials
and working customer URLs out of examples. Use native paths with correctly escaped
backslashes in FileMaker string literals.
For FileMaker editor and installation controls, the getting-started guide links to current official Claris help. Product-specific claims are grounded in this repository rather than third-party plug-in documentation.