Now that the new Save as XML feature exists, one of the early uses is to plug that information into a free tool from Geist Labs that shows a complete edit history of the file; who modified what when.
All data is processed locally on your machine so no security issues.
It compliments the paid FMComparison tool and provides a different set of information. Someday maybe Claris will have real software configuration management but until then this is a small but useful step in that direction.
Note: the save as XML is now scriptable as well. Having a daily version can prove useful.
So how do you get the XML formatted FM code back into script workspace?
Script Workspace's auto-complete and tight typechecking is available outside script workspace?
I need some "edumacation" in how this would work. I know that Dan Shockley has a set of FileMaker Applescript functions that support a lot of FM code interaction, and can be combined with RayCast to do some amazing things, but not had the time to go through the required configuration to get there.
@Kirk If you're interested in doing fm2xml and xml2fm conversions and storing xml snippets that can be pasted into FM on the fly, I made a (very rough) video about this years ago for a friend, and I've had quite a few people find it and use it as a launchpad for what you described since then.
I desperately need to rerecord this video for public consumption with clearer instructions and less muttering, but nonetheless some people have found it helpful for getting started using Dan Shockley's FMClipTools and a textexpander/typinator or your choice.
It's been a gamechanger for me personally, and I think others as well. MASSIVE productivity boost when coding, far beyond copy-pasting from templates. Basically auto-complete for entire script blocks, fields, layout objects, custom function suites, etc.
uh I don't get it, my filemaker save as xml prouce a file where all objects' timestamps are set to the time of saving has xml.
So the tool works, but it's pretty useless to me, since Filemaker (latest 20 version) botches the modification timestamps