Dynamically create each module as a standalone plugin

[sjcross]

Each module could be run directly from ImageJ's plugins menu (e.g. Plugins > MIA > Modules > ... - getting rid of the WBIF_Bristol part for simplicity). Running a module would open a simple dialog (like ImageJ's GenericDialog) that gives options for all the parameters.

Input images could be selected from either standard image windows open in ImageJ or those in the active MIA workspace. The input image list could be split ("--- From ImageJ ---", list of windows, "--- From MIA workspace ---", list of MIA images); an example of adding separators to a list is the parameter for listing modules (e.g. used for module redirection).

Objects would have to come from the active MIA workspace. As such, this would be tidiest when the ability to dynamically select workspaces has been implemented.

Since there would be no module list to determine availability of measurements/relationships when selecting, for example a parent collection, it would be up to the user to ensure what they've clicked is reasonable. Active relationships could be tracked, but this would require a separate mechanism and this could get messy (maybe something to include further down the line).

Modules run in standalone mode should be compatible with the ImageJ macro recorder, thus providing an alternative route to generating a workflow. This would also supplement the hard-coded MIA macros.