Scripters Club Recordings: Managing Your JMP Add-Ins

[#1]

In this Scripters Club session, Justin Chilton, the developer behind the popular Add-In Manager on the JMP Marketplace, will showcase how to better organize, update, and deploy your JMP add-ins. Learn how this tool can simplify your scripting workflow and improve how you manage and share your custom solutions.

Video 1: Managing Your Add-Ins

Video 2: Updates on add-in builder, view add-ins

[#2]

When you create and install an add‑in for the first time, it appears in the Developed Add‑ins section.

In the deployment setup, there are two folders: Test and Production. If you want to maintain two separate versions, the add‑in must also be saved into those folders.

The annoying part is that you have to reinstall the add‑in even though you just install it the first time when you get the add-in in the developed add-in section and to update the update the path for the Test and Production.

Another question is how this works when you modify the JSL file and include it in the add‑in as an external file rather than embedding the script directly. How does JMP handle updates in that case?

[#3]

Actually, I might be wrong but still.

When a user creates the add‑in, they don’t need to install it. The add‑in will still appear under Developed Add‑ins, and from there the user can specify the paths for the test and production environments so that JMP can copy the add‑in to those locations as well.

However, the user must manually create those two folders beforehand.

One thing I’m still unsure about is how updates work in this case. If you include a JSL file in the add‑in and later make changes to that file, will the user receive an update notification based on the updated JSL file included in the add‑in?

Or do we need to unselect the file in the add‑in builder and re‑select it again so that JMP packages the updated version?