![]() ![]() Those are all the steps that I need to complete the configuration of the add-in. Once I’ve added the Resources directory the final list of files should look like this: I only want to include the first two files I can get rid of the others using the Remove button. Once defined I want to associate the JSL script Oneway Advisor to the menu item:įirst I need to identify the directory containing the include files:Īll the files in the folder are identified. I only want a single menu item, “Oneway Advisor”, to appear under the JMP Add-Ins menu. It can include periods, hyphens and underscores but not spaces. ![]() The entire string can be up to 64 characters in length. Whilst you are free to choose any value for the ID, the following naming convention is recommended by JMP: This is the only mandatory field, and must be unique to avoid conflicts with other add-ins. I need to provide a name and unique identifier for the add-in:įrom JMP’s perspective the critical piece of information is the ID. I’m now ready to use the JMP Add-In Builder. My original code assumes that my include files are in the same folder as the main script: This means changing my code to ensure that the files can still be found now that they have new relative locations. My main script is at the top-level, and then I have sub-folders containing the include files and resource files. I’m going to choose to reorganise the files so that they have the structure shown on the right-hand side. If I want Oneway Advisor to be in the “home” directory then I’d like one of the following file configurations: In particular I would like the main script ( Oneway Advisor– the one that will be attached to the Add-Ins menu) to be located in the “home” folder, and for all my other files to be visible relative to this location. Project Preparationīefore using the Add-In Builder I will save myself a lot of trouble by giving some thought to the organisation of my files. Usually we don’t care about the specific location, but it’s important to understand that all the files need to be accessed relative to this location. When the add-in is installed all the files will be deployed in a new location which is referred to as the “home” directory of the add-in. On the Menu Items tab I will identify the JSL file that is executed when a menu option is selected, and all the additional files will be identified on the Additional Files tab. On the General Info tab I will provide the name and unique identifier for my add-in. The add-in builder is launched by selecting File>New>Add-In.Ī tabbed-window is displayed into which I need to provide all relevant information. I’m going to walk through the use of the Add-In Builder by using it to create an add-in for the oneway advisor. In order for JMP to interpret the file as an add-in file, the file extension needs to be changed from zip to jmpaddin.īut there is an easier way, the Add-In Builder. It’s possible to create the zip file manually. The menu file defines where the add-in will appear on the JMP menu system, what the menu structure will look like (you are not limited to a single menu item), the names of the menu items and the actions performed when a menu selection is made. If you know that you are using new features of JMP then the definition file can also contain the minimum version of JMP required to install the add-in. The only mandatory information required for the definition is a unique identifier. The add-in definition file is a simple text file that follows a standard template. In addition to these files there are two additional files that need to be included: The zip file contains all the files associated with the JSL application (in my example there are 6 files). What Is An Add-In File?Ī JMP add-in file is simply a collection of files that have been “zipped” into a single file. This means that I need to configure the menus and then send my colleagues not only a JSL file but also a menu configuration file. The most convenient way to do this is to have the script attached to the JMP menu system. The most convenient way to do this is to have the script attached to the JMP menu systemBut even if it were only a single JSL file I would like to provide a way of making the script easily accessible and easy to run. ![]()
0 Comments
Leave a Reply. |