FileMaker itself remained mostly closed.Īll of that begins to change with FileMaker 19. The calc engine and script engine were also out of reach, unless you opted for plugins, which required a C developer to write and didn’t work on the whole platform. We couldn’t use calendars, or photo editors, or kanban boards or D3 charts any easier than before. But FileMaker 16 didn’t make it any easier to build rich interactive experiences inside of FileMaker. We could reach out and interact with the internet we could even pull data back into FileMaker and display it. Just a few years later and just about every project we do connects to one or more APIs, and JSON has become the de-facto way of passing data around in our solutions.Īll of this was great, but it but it didn’t change what we could do on a FileMaker layout. Overnight, we gained access to thousands of APIs and services that are available over the internet. It was the first release that natively supported connecting to the global API economy. In my FileMaker 16 release blog post, I focused on the integration features we gained. Yes, it was… but that was 4 versions ago. The Calendar Heatmap was built by our own Jeremy Brown using an open source add-on framework we created at Geist Interactive as part of a collaboration with iSolutions and Claris Engineering teams.
The add-on builder feature has been released as a Developer preview in FileMaker 19. The user of the add-on doesn’t need to know anything about how the add-on is constructed to use it. This Add-on is a mixture of JavaScript and FileMaker. You can drill into a FileMaker Card window to get more detail on each days’ events. It shows the number of events that have been scheduled on each day for a given 3 month block of time. Once in browse mode the Add-on just works. The little clip above shows a Calendar Heat Map Add-on being dragged out onto a layout, just like it was any other FileMaker control.
0 kommentar(er)
