cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Choose Language Hide Translation Bar

Add-in Script Converter between Versions

What inspired this wish list request? 

I've experienced migrating scripts & add-in from JMP 15 to JMP 16 to JMP 17 which consume a lot of my engineering time to debug.

We never know how many more versions JMP plan to release in the future.

I foresee we will keep repeating this process, which really holding us back to fully automate the decision-making flow in operation.

Imagine, if I have 10 scripts saved at 5 computers for machine learning which may contain >100 lines of code.

Every time JMP release new version that is not compatible with old versions, I need to re-edit my scripts & test at all computers to ensure no disruption to the operation.

 

What is the improvement you would like to see? 

-Create "add-in script converter" between versions. Maybe start with JMP 17 --> if user want to upgrade to JMP 18 license, this feature propose a new script or verify the old version code to see if it compatible. 

-Maybe add this feature in "add-in manager" feature highlighted by other users.

https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/ta-p/43736#U43736

https://community.jmp.com/t5/JMP-Wish-List/Integrate-Add-In-Manager-in-Jmp/idi-p/575114

 

 

Why is this idea important? 

1. We can save a lot of time & do something else in JMP rather than keep re-edit our released scripts.

2. Easy for me to justify investment to buy more JMP license.

 

1 Comment
guillaumebugnon
Level V

100% agree with this suggestion.

Migration of scripts from one version to another takes a lot of time, and this slows down rapid version upgrades.