Video BrowserNavigation |
ZippScript Script Triggering Plug-inPosted by: Editor / Tuesday, March 20, 2007 – 8:06pm
zippScript is a very powerful script triggering plug-in. You can use it to trigger scripts based on actions within the FileMaker user interface (your layouts). You can trigger scripts based on record creation or deletion, when you edit a record or exit a field. [Extracted from the example file] zippScript 2.0 adds powerful script triggering and script scheduling toolsto your programming toolbox. With this plug-in you can:
The original zippScript was one of the first FileMaker® Pro 7-native plug-ins to be released and the first free script-triggering plug-in to provide the critical ability of passing a parameter string to the triggered script. zippScript 2.0 builds on this solid foundation by adding the ability to schedule a script to be triggered at some future time and adding functions to temporarily disable script triggering while performing scripted record updates. zippScript 2.0 is compatible with FileMaker Pro 7 and later, and will run natively on Mac OS X (PPC), Mac OS X (Intel) and Windows. It is a drop-in replacement and upgrade for zippScript 1.1. Commercial developers are encouraged to consider making a donation to help fund continued development and support of this and other FileMaker utilities. If the functionality of this plug-in adds value to your solution, please click the “Make a Donation” button and contribute whatever you feel. Filed under: plugins | Free Access
. Plug-ins download to the client machine. - ADMIN POSTED THIS.
. Editor said this on Thursday, March 22, 2007 - 8:25pm.
. Server does not execute* the commands which a plug-in implements. There are new features in the latest versions of Server (7,8) which do allow some processing a plug-in may need, to be “offloaded” to the server side so it can process prior to shooting data back to the client. *This is what FileMaker calls “server side” plug-ins - although the plug-in is still on the client site, the server just handles some of the processing. In the case of zippScript, there’s no need for server side processing. The execution of a script is initiated client side. Server also provides the feature of downloading a plug-in right to the client. The client does not need to be restarted to take advantage of the plug-in features. This happens via the AutoUpdate plug-in that is automatically installed into any copy of FileMaker. This has been around since 5.0. Follow this link for FileMaker, Inc’s instructions on how to do this. You can also automate this in an easier way by using a product from 24U Here are some other articles from the FileMaker Inc Knowledge Base How Automatic Downloading Works With The Auto Update Plug-in Understanding The External Functions Of The Auto Update Plug-in Auto Update Plug-in Configuration Overall, plug-ins used to be a scarry proposition back in the day when they were first implemented. Today, however, you should take advantage of as many plug-ins necessary to make your solution sing. Once you’re comfortable using them, it’s “no big deal” to add one more (unless licensing is your bigest issue.) As you probably already know, I favor the new PHP plug-in from Scodigo.com! . |
Be notified!Sign up for any of our notification lists for the quickest notification of new items! iPod Video
FileMaker Reference Tool10 Most Recent Videos
|
ZippScript
Is ZippScript working under filemaker server ?
I am always a bit affraid with plug-ins if you work in a server environment .