Directory | Changes | Lines of Code | Lines per Change |
---|---|---|---|
Totals | 14 (100.0%) | 909 (100.0%) | 64.9 |
plugins_SDK/templates/ | 6 (42.9%) | 550 (60.5%) | 91.6 |
plugins_SDK/ | 2 (14.3%) | 188 (20.7%) | 94.0 |
src/dr/app/plugin/ | 4 (28.6%) | 156 (17.2%) | 39.0 |
src/dr/app/beast/ | 1 (7.1%) | 13 (1.4%) | 13.0 |
/ | 1 (7.1%) | 2 (0.2%) | 2.0 |
This commit adds a script and template files to the plugins_SDK directory (no
changes to java source code in BEAST). The directory now contains a simple
python script that will create a stub for a BEAST plugin. This is primarily a
matter of copying some file templates and changing names to the name that the
plugin author chooses). The plugins_SDK/README describes how the script should
be used. In addition to creating source code stubs, the generate_stub.py script
will creat an ant file with appropriate targets and a simple XML instance
document that uses an new XML element (that the plugin must parse).
Most of this code was written at the NESCent BEAST working group. Version
control for earlier versions of this is via git at
git@github.com:mtholder/beastPlugin.git
738 lines of code changed in 8 files:
The plugins directory can now be specified as a system property beast.plugins.dir this property should not be necessary when running beast through an IDEs, but is needed when invoking from a terminal from a different directory. Perhaps the need for the property can be removed -- from inside the IDE the plugins directory is found because it is a subdir of the top of the beast tree
22 lines of code changed in 1 file:
removing path to a local file on my machine that was inadvertently committed the previous commit
1 lines of code changed in 1 file:
Beginnings of the Plugin system implemented
148 lines of code changed in 4 files: