- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
Extracting the script behind addins
Is there any way I can extract the script behind add ins like the Table Attributes add in or Limits to data table add in?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
Re: Extracting the script behind addins
Addin have their JSL available in one of two structures. And it turns out, the two Addins you referenced happen to cover both structures. The JSL for the Table Attributes was saved as separate files for the Addin. Because of that, you can go to the folder for the Addin and directly see the files. To find the folder and to branch to it go to
View==>Addins
It will popup a dialog box, where you can select the Addin you want, and then the selection will provide you with the folder(directory) the Addin is stored in.
The second Addin structure, has the JSL saved directly in the Addin menu definition. To access this type of Addin, you will need to edit the .jmpaddin. To access this file for the Limits to Data Table, you will need to save the Addin file to a local disk, from the File Exchange, rather than just installing it. Once it is saved, go to
File==>Open
and navigate to the file you downloaded and saved. Click on the file, and then go to the down arrow next to the "Open" button and select "Open using Add-in Builder". Then click on OK. The Add-in Builder will open the Addin and within the Menu item for the Addin, you will see the embedded JSL.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
Re: Extracting the script behind addins
@txnelson,
Is it possible to completely hide the script behind any addin except for the author
Uday
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
Re: Extracting the script behind addins
The way you do this is to encrypt the script giving it a password that has to be specified for the user to view the source.
See "Encrypt and Decript Scripts" in the Scripting Guide
Help==>Scripting Guide