Scripters Club Recordings: Managing Your JMP Add-InsIn 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
Re: Scripters Club Recordings: Managing Your JMP Add-Ins
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?
Re: Scripters Club Recordings: Managing Your JMP Add-InsThis is late but maybe other persons as myself are looking the topics.
There is how I worked around this situation. Maybe there is other ways but that's working.
So there is a Main_script.jsl opened in the addin command calling a functions_script.jsl that is placed in the Included Files tab.
When I modify function_script:
- I open the add in view in developed add-in tab,
- click edit on the concerned add-in
- say yes to update files
- go in the general info tab
- increase the version number
- save the add in
that allows JMP to know that the addin changed and needs to be updated in test or prod folder.
Then it is a matter of version handling and releasing.
