Should offer the ability to "plug in" additional plugin modules.

Flywire should offer some ability to add external classes to the interface to offer a more structured/less monolithic architecture for expansion.

Currently if we want to add features we have to modify the core code and release a separate binary for each combination of option. This is already becoming difficult to manage, and isn't for future expansion or good for new, or testing development.

There is currently no technical proposal for how we want to offer plugins. This should be the focus of a meeting soon. My preferred choice would be to NOT use an external plugin provider, e.g. eclipseRCP, but instead to apply the KISS principle.

For example, a simple "plugins" directory could be used to house the plugins, and then a text file could be used to manage which ones were loaded. This directory and file could either be used by each user and be housed in the user's directory, or by the system. The order of authority would be important here, unless we offered the user an ability to "disable" a system plugin by cross referencing the two text files.