Large JavaScript Bundles may be broken up into several “Insert text” script stepsĬarafe Kitchen has a solid deployment process that is streamlined, keeping the HTML with JavaScript embedded in the script and easily maintainable. Uses substitute on variables - can be slow on large data sets Structured example for passing a parameter to the script - makes it easy to pass data as parameter into the script Here is a breakdown of the pro’s and the con’s I found during my exploration:Įasy deployment process - select the bundle and click deployįileMaker centric code - easy for a FileMaker developer to maintainĮxample data preloaded by default - makes it easy to test It ultimately meant you were managing several workarounds and possibly creating technical debt problems down the road. This process sometimes included embedding it in sneaky ways so that it could survive cloning of the solution. You had to wrap up the HTML with JavaScript yourself and come up with different techniques to access and maintain that code. Implementing JavaScript content efficiently, on the other hand, had previously been a little difficult. FileMaker developers have been able to utilize a web viewer and render JavaScript-driven content since FileMaker 16. It isn’t a new concept, but it has been well thought out. The process seems magical, and is very clean and simple. Then, to finish it off, add a web viewer object to a layout, name it “web”, and you can see the results. You simply paste the script, containing everything you need sans a web viewer, into your solution. Once you pick the bundle you like, you click to deploy and it is copied to your clipboard by way of the Base Elements plugin. You’ll see a list of bundles that have been submitted by the community. By doing so, they are easy to modify and adjust after you have put them in your own solution. For the purpose of this blog, I am going to focus on Carafe Kitchen, as it has been the tool I prefer.Ĭarafe Kitchen allows you to configure and deploy the various Carafe bundles by wrapping them up into a single script. While I think the Carafe Add-on is a pretty cool idea, as it allows you to use the add-on feature in FileMaker to dynamically install unlimited bundles into your solution, I really love the simplicity and ease of using the deployment process that the Carafe Kitchen provides. They are Carafe Add-on and Carafe Kitchen. There are two FileMaker solutions for Carafe that provide easy access to some of the community-driven bundles. To get started, just download one of the Carafe solutions. You can use it to install JavaScript add-ons, deploy JavaScript libraries that are wrapped into a single script, or even build bundles for the community to share. It provides a community for building and sharing JavaScript bundles that have been streamlined for use with FileMaker. Carafe Kitchen has been one of the most exciting FileMaker tools for me this year.Ĭarafe.fm is a community bundle sharing resource for FileMaker, sponsored by Soliant Consulting. After struggling to roll my own implementations that could be maintained easily, I was relieved and excited to find this valuable tool. With all the new features in FileMaker that are supporting JavaScript, the one thing that I found lacking and still difficult to overcome was a solid process for managing and implementing JavaScript libraries. With Carafe Kitchen, implementing JavaScript into your Claris FileMaker 16+ solutions has become as easy as copying a script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |