Plugins can be developed to augment TSTool's built-in functionality. These are listed in the Plugin Reference documentation. Installing plugins and checking for new plugin versions could be streamlined with a "plugin manager". Other software such as Eclipse and Visual Studio Code has similar features. These initial plugins could serve as the basis for an initial implementation.
There will be some complexities such as knowing where to look for plugins on the web (maybe TSTool could maintain a TSTool plugin registry with a list of plugins?) and the technical work to integrate metadata from different plugins. Some basic requirements already exist for plugins.
Moving some existing code to plugins, such as Reclamation HDB could also simplify the core TSTool product for maintenance in OpenCDSS and would remove some clutter from the core product, thereby simplifying training.
Subject of the issue
Plugins can be developed to augment TSTool's built-in functionality. These are listed in the Plugin Reference documentation. Installing plugins and checking for new plugin versions could be streamlined with a "plugin manager". Other software such as Eclipse and Visual Studio Code has similar features. These initial plugins could serve as the basis for an initial implementation.
There will be some complexities such as knowing where to look for plugins on the web (maybe TSTool could maintain a TSTool plugin registry with a list of plugins?) and the technical work to integrate metadata from different plugins. Some basic requirements already exist for plugins.
Moving some existing code to plugins, such as Reclamation HDB could also simplify the core TSTool product for maintenance in OpenCDSS and would remove some clutter from the core product, thereby simplifying training.
Environment