On the topic of getting AI generated code (scripts et al) into FileMaker there are two camps:

1. backdoor people, who purport the use of the FileMaker Update Tool to patch code into solutions
2. frontdoor people, who use the FileMaker Client GUI to 'do work as normal' and (mostly) use the FileMaker clipboard (fmxmlsnippet et al) to grab & patch code

Whilst API-based AI-interaction is, of course, the automation dream we strive for (and odata already provides great possibilities here) the FileMaker Update Tool is still very wanting in a multi-developer server environment (dare I say useless for now?), and I am thus very much (at least for the time being) in the frontdoor camp.

To boot I have a host of tools for enhancing the FileMaker GUI for increased productivity here (see fmWorkMate.com and one of them has an important role to play in the new era of AI…

fmIDE - a FileMaker Integrated Development Environment - is an integration tool (a one-script (*) module for each of your FileMaker files) which opens up a bridge between your AI agent and the FileMaker GUI.

With the fmIDE 'Name that Thing' API you / your AI can jump to any (**) thing in FileMaker in a single click (***).

With fmIDE Action Scripts - and the newly emerging and very exciting fmJAML format - you and your AI are also able to write dynamic action scripts that can not only select steps in scripts, but also replace the code.

fmIDE is already integrated into BaseElements, now also into Marcel Moire's coming AI tool, … and could soon be on your desktop.

Approximate content:

- State of AI FM-Code generation / FM-Challenges / step text, xml & co. / getting code back into FM: frontdoor/backdoor camps

- A short (re-)introduction to fmIDE, what it does, where it fits in to the modern AI supported code generation:  as an action bridge between AI and FM.

  - fmIDE Name that Thing API

  - fmIDE action scripts

  - Diagramme of how fmIDE works inside

- JSON as a structured data language - limitations ('fluffy')

- JSON in FileMaker: JSONSetElement pros and cons

- fmJAML "FileMaker JaSON Markdown Language" (short presentation)

- hardening fmIDE for real world use: Proof by Testing (thanks to fmJAML)

- (frontdoor) Actions for AI / Rename Script / Update Script / etc.

- conclusions / discussion / celebrations / dancing: potential, limitations, to dos, documentation, help!…

Oh yes: and (crazy MrWatson) proof why you need fmJAML in FileMaker

You might want to not miss this. C U in Vienna!

MrWatson

(*) +2 optional customising scripts

(**) nearly any

(***) P.S. I'm not great at counting beyond one :-D