losarunning.blogg.se

There’s even plug-ins for making plug-ins and popular open source plug-ins.įileMaker version 12 introduced the Install plug-in script step, making it incredibly easy to install plug-ins for desktops and server editions. For instance, the MonkeyBreadSoftware plug-in, alone, encompasses over 4,600 functions. Fast forward 20 years, and there are plug-ins that cover the full spectrum of bolt-on functions for FileMaker.

So, why use plug-ins? The plug-in architecture was first introduced because FileMaker realized that they’ld never be able to cover all desired functionality that app developers would want. The FileMaker iOS SDK (that allows us to create fully compiled apps for iOS) was released with version 15 in May 2016.A year later, FileMaker has completed the functionality puzzle with the plug-in addition in FileMaker 16. FileMaker Go was released in 2010, making it a mature product of seven years. While the plug-in architecture has been updated over time-for example, to update and allow for 64-bit plug-ins-the functionality of the plug-ins has gone relatively unchanged for 20 years. Plug-ins were introduced to the FileMaker platform all the way back in Version 4, released in September of 1997. And that’s not all… FileMaker Go also supports the new plug-in SDK features of creating your own custom script steps, so now the FileMaker Go plug-in engine is just as powerful as the desktop one.

Since the plug-in SDK now supports Linux, FileMaker has brought support for plug-ins to all corners of their product line. I’m referring to the new FileMaker Go plug-in SDK, of course. With all the new features in FileMaker 16, few have been discussing one of the biggest advances to FileMaker’s iOS presence…