Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tutorial:plugins [2020/12/28 23:40] admin [Develop custom plugin] |
tutorial:plugins [2021/01/10 17:58] (current) admin [Using Custom Plugin] |
||
---|---|---|---|
Line 6: | Line 6: | ||
* [[#Deploy custom plugin]] | * [[#Deploy custom plugin]] | ||
* [[#Using custom plugin]] | * [[#Using custom plugin]] | ||
+ | |||
===== What does a plugin do?===== | ===== What does a plugin do?===== | ||
Line 16: | Line 17: | ||
Before we can start building our custom plugin, we need to set up the java development environment: | Before we can start building our custom plugin, we need to set up the java development environment: | ||
- | * create a java project | + | * create a java maven project |
* add following maven dependency to pom.xml | * add following maven dependency to pom.xml | ||
+ | |||
< | < | ||
< | < | ||
Line 23: | Line 25: | ||
< | < | ||
</ | </ | ||
+ | |||
Now we are ready to build our first custom plugin in Eclipse: | Now we are ready to build our first custom plugin in Eclipse: | ||
Line 29: | Line 32: | ||
* add @TO_PLUGIN annotation to your java class | * add @TO_PLUGIN annotation to your java class | ||
* implement required methods | * implement required methods | ||
- | * add your plugin functions, declare as public functions | + | * add your plugin functions |
Below is an example of the java class: | Below is an example of the java class: | ||
Line 70: | Line 73: | ||
} | } | ||
- | By default, all public methods declared as well as inherited are exposed as MScript function. | + | By default, all public methods declared as well as inherited are exposed as MScript function. |
Don't forget to write junit test to test the plugin functions. | Don't forget to write junit test to test the plugin functions. | ||
Line 76: | Line 79: | ||
===== Deploy Custom Plugin ===== | ===== Deploy Custom Plugin ===== | ||
- | Export project as jar file | + | * Export project as jar file |
- | Copy plugin jar file to /lib folder in // | + | |
- | Register your plugin package in config.properties: | + | |
| | ||
Line 84: | Line 87: | ||
Above registry tells // | Above registry tells // | ||
- | Restart TestOptimal server to make the changes effective. | + | * Restart TestOptimal server to make the changes effective. |
===== Using Custom Plugin ===== | ===== Using Custom Plugin ===== | ||
- | Open an existing model or create a new model | + | Plugins must be activated before they can be used in the script. |
- | Select | + | |
- | Click on " | + | * Open an existing model or create a new model |
- | Check the checbox | + | |
- | Your plugin should show up on CodeAssist list as // | + | |
+ | | ||
+ | * Close Plugin Activation dialog | ||
+ | |||
+ | Press // | ||