10-31-2019, 01:59 PM
Yes, actually the source code has a few already. In fact, looking at the code, the zip of the vfx template is actually a plugin. I am not sure why creating a project with the vfx template doesn't just load the plugin ... it must, but the plugin isn't registered for some reason.
At any rate, the plugins that all the unittest use can be found in:
<TACTIC_INSTALL_DIR>/src/plugins/TACTIC
The vfx zip can be found in:
<TACTIC_INSTALL_DIR>/insta../start/templates/
Basically, the plugin manager looks at custom plugins in the folder:
<TACTIC_DATA_DIR>/plugins
A plugin is just a folder with a manifest.xml file. The manifest file determines how to export data from the database and dumped into ".spt" files which are basically just python code made to look like data. This manifest is also use to load in a plugin from the spt files. This manifest file determines which rows in the database are "owned" by the plugin. With this you can export search type defintion and widget config entries (which will include any custom widgets). You can also export data if you wish.
And within a plugin folder, you can also put any python files for classes and any other extras like css file and js files if desired. So we place any custom code in here as well. Then we zip up the folder and can deploy to any other TACTIC server. This is kind of similar to Wordpress plugins.
At any rate, the plugins that all the unittest use can be found in:
<TACTIC_INSTALL_DIR>/src/plugins/TACTIC
The vfx zip can be found in:
<TACTIC_INSTALL_DIR>/insta../start/templates/
Basically, the plugin manager looks at custom plugins in the folder:
<TACTIC_DATA_DIR>/plugins
A plugin is just a folder with a manifest.xml file. The manifest file determines how to export data from the database and dumped into ".spt" files which are basically just python code made to look like data. This manifest is also use to load in a plugin from the spt files. This manifest file determines which rows in the database are "owned" by the plugin. With this you can export search type defintion and widget config entries (which will include any custom widgets). You can also export data if you wish.
And within a plugin folder, you can also put any python files for classes and any other extras like css file and js files if desired. So we place any custom code in here as well. Then we zip up the folder and can deploy to any other TACTIC server. This is kind of similar to Wordpress plugins.