Examples of use cases? #2
Comments
This project lets you write FileMaker plugins completely in Common Lisp. With this project you don't need to write any C/C++ code and you can use LispWorks to generate/deliver binary FM plugins (essentially a dynamic library or DLL). The user must be experienced Common Lisp programmers and owns commercial licenses (professional edition is fine, but still quite expensive) of LispWorks. One big use case is inside the Hope this helps, and feel free to ask more questions. |
|
Thank you very much for the details. I do have a Hobby DV LispWorks 8 license for Mac, but I am not an experienced Common Lisp programmer. I see a Win32 lisp file in the I would follow the documentation. |
Yes, with a Hobby DV version you should be able to build the regex-plugin example on your M2 Mac. The resulting plugin, of course, can only be loaded in M2 version of FileMaker on macOS. But I've never tried with M2 Mac, as I only have Intel MacBook Pro and my FileMaker Pro version is 18 (Intel only). It would be interesting to know if you can build it. (However, with Hobby DV license you may not distribute the resulting plugin, if succeed. But I'm not so sure, check with LW people.) You may need to modify the some scripts, to reflect your actual installation directory of LispWorks. Let me know if you meet any issue, either specific to M2 Mac or to higher versions of FileMaker. |
|
I will, thank you very much. |
|
I have fixed the documentation page: https://binghe.github.io/fm-plugin-tools/ |
|
Thank you for pointing it out, it is helpful to have it online. I have downloaded the Plug-in SDK for Mac and I am studying that documentation. |
|
I am having trouble creating the bindings to the C header files, the Listener returns: This is what I do: After cloning |
|
I solved this step by executing, |
|
Running |
|
Looks good, but can you actually load it in FileMaker Pro? |
|
Besides, this is NOT the regex plugin but the other smaller example. You can use the delivery scripts inside the |
|
Ah, you are right of course! Launching Filemaker, I do not see the plugin in I am now going to run the script from the inside the |
You need to copy the plugin bundle into FileMaker's plugin folder - the exact location depends on FMP version, it can open the folder for your from the settings, then you just copy. There will be extra security warnings since the plugin is not code-signed, you need to modify your macOS privacy settings to let it pass. FileMaker itself may also complain that the plugin does not have certifications, which is another different requirement then code signing. If everything is done correctly, you should be able to load the plugin, but it won't create any new menu items. Instead you need to create a database and see if you have more custom functions available. |
|
Delivery is successful, but the scritp cannot copy the plugin with this error: Changing line 36 of from: allows the script to copy the plugin. But launching Filemaker Pro does not show the plugin in the Preferences > Plugins setting pane. By clicking on 
|
|
I have tried to compile with Plugin is compiled and copied over in the proper directory, A freshly launched FileMaker does not see the plugins. I tried with other third-party plugin in same directory, .i.e BaseElementsand they are seen. How could I go about debugging this issue? |
|
You can set the variable If, unfortunately, after enabling the log, such a log file doesn't exist at all. This will mean that the code inside plugin didn't execute at all, and this means the translation of SDK header files has some problems due to FMP version changes, or the new ARM64 platform. Then this is harder to fix for me, without actually having a Mac with Apple Silicon processors. |
|
Thank you so much for the code, very instructive! Where shall I include it, in |
That function is already in |
|
Thank you. I have added that line in My school has FileMaker for Windows, and may have a LispWorks Windows license. I could try to compile it there. Would that help? |
|
If I found time, I will first make sure the last PluginSDK works on Intel macOS, and then confirm with x64 Windows. This may involved some actual code changes in the C++ header parser, and perhaps it will cause some positive changes on your side. |
|
Thank you very, very much for your help and time. I am learning a lot from this process. Will you let me know if there is anything I can do. For sure I could test building on Mac M2, and I believe I could on Windows 10/11 as well. Thank you again. |
|
Hello there, I can confirm that this project currently doesn't support FileMaker SDKHeader version 20. If I use SDKHeader from 18 to build FM plugins, the resulting plugin can be correctly loaded into FileMaker Pro 20 (2023) on Intel macOS and x64 Windows. But FileMaker Pro 18 doesn't support ARM macOS, and I don't think you can use old SDK headers to generate working plugins for FileMaker Pro 20 on ARM64 macOS. I need some time to analyse the differences between SDKHeader 18 and 20, and fix the SDK parser. |
|
Thank you for the confirmation, very much appreciated. Please, let me know if/when I can be of any help by testing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am much interested in combining LispWorks and Filemaker Pro, but I am not an experience Lisp developer, and I failed to see use-cases that can help me understand what
fm-plugin-toolscan do.Is this perhaps similar to FMProKit?
How can one use
fm-plugin-toolsas a bridge between LispWorks code and FileMaker?The text was updated successfully, but these errors were encountered: