August 16Aug 16 Hi everyone,I'm in private aviation, running FileMaker in-house solutions for about 13 years. To stay on track with AI development I've built a few small tools. Eventually I decided to pack them into a native FileMaker plugin, so it's one tool instead.The three biggest problems it solved for me:I am in control of what the AI sees. Everything runs locally, no network calls during conversion, works offline. Nothing reaches an AI except what I paste there myself.Accidental secret leaks. If the steps I'm copying contain something that looks like a password or API key, the copy stops and asks. One click replaces the values with placeholders. It's a heuristic scan, so a safety net, not a guarantee, but it has caught real leaks for me.Read-proofing code before it goes back into FileMaker. Whatever the AI changed comes back as plain text I can actually read and check. The plugin also round-trips every conversion against itself before writing to the clipboard; a conversion that doesn't survive its own check refuses instead of pasting something corrupted.Mechanics: select scripts as batches or single, or script steps, ⌘⇧C — the clipboard now carries the script as text, paste it anywhere (any editor, any AI, git). Copy the edited text, ⌘⇧V in the Script Workspace — it converts back and pastes as real scripts or steps.For AI: there's a calc function that copies the text-format spec (it does not contain your context!), so an AI can write new scripts from scratch in that format too.Beta: free, macOS 14+, FileMaker 2025/2026 (older versions untested). If it might be useful for you, sign up at https://fmscriptbridge.com and I'll reply with the plugin. Windows version is in progress.If something breaks or converts oddly, there is a bug report feature (you control what is reported)I will be thankful for your feedback.Victor
September 4Sep 4 Author Dear All,The 0.9.24 version of FMScriptBridge is out. The plugin now accepts a broader variety of generic FM script steps, so it is easier for you guys to copy code snippets from here, for example, straight to your code.One caveat though: curly quotes ” are not widely accepted, so they may throw errors. I am working on that.It also accepts MBS commands! You can try it out below.If you do not have MBS or it is disabled our you have an older version which misses functions, the FMScriptBridge plugin evaluates and adds a warning comment.# Load Saxon in file Saxon Visualize electronic Invoices Set Variable [ $path ; Value: "" ] # you may need to put in your path or have the libraries in the folder for the plugin If [ MBS("IsMacOS") ] Set Variable [ $path ; Value: "libsaxon-eec-12.10.0.dylib" ] Else If [ MBS("IsWindows") ] Set Variable [ $path ; Value: "libsaxon-eec-12.10.0.dll" ] Else If [ MBS("IsLinux") ] Set Variable [ $path ; Value: "libsaxon-eec-12.10.0.so" ] End If # Set Variable [ $r ; Value: MBS( "Saxon.Load"; $Path ) ] If [ MBS("IsError") ] Show Custom Dialog [ "Failed to load saxon library." ; $r ] Halt Script End Ifhttps://fmscriptbridge.com/changelog/
September 15Sep 15 Author Dear All,The 0.9.25 version of FMScriptBridge is out. Remember the curly quotes caveat from last time? That is fixed. Curly quotes in script, layout, menu set and table names now convert as written.The secret scan on copy got a lot of work too. It is far faster now: a very large copy that used to take minutes takes about a second. It also spots many more credential shapes, like passwords passed to BaseElements and MBS functions, passwords inside connection strings and private keys. And it no longer flags masking code such as Substitute ( … ; "password" ; "********" ).One more thing: the plugin now accepts more of FileMaker's own display forms when pushing. You can try it out by writing Open File with just the file name and pushing it.If you want to try it, sign up for the beta here: https://fmscriptbridge.com/#beta
Saturday at 09:46 AM2 days Author Hi guys,FMScriptBridge 0.9.26 is out. Happy to announce that it now supports multi-file work for schema reference checks: paste into any file's Script Workspace and the references get checked against that file, not just the one FileMaker considers current.Also added support to paste raw FileMaker XML (plain text, no special clipboard flavor required). It goes through the same routine: missing reference checks and calculation checks! No matter what your AI gives you, the plugin can handle it.One caveat though: when you paste into a file other than FileMaker's current one, the calculation check does not run and the warning tells you so. Click that file's own window (not its Script Workspace) and convert again. FM limitation we have to deal with.Last but not least: added AI Specs versioning per plugin release to ensure proper AI trainingIf you want to try it, sign up for the beta here: https://fmscriptbridge.com/#betaThank you and have a wonderful day.Victor
Create an account or sign in to comment