New Developer Features in GIMIAS 1 6

From user's Wiki!
Revision as of 03:02, 14 January 2013 by Xplanes (Talk | contribs)

Jump to: navigation, search

GIMIAS-1.6.r1 (in progress)

FIX #0417: GIMIAS takes 20 sec. to start in debug mode

Enabling just the MITK and SceneView plugin, GIMIAS takes 26 seconds to start in Debug mode. It will be interesting to reduce this start-up time for developers that are working on a GIMIAS plugin.

To analyse the start-up, the VS2010 profile tool has been used. Most of the time is taken when initializing OpenGL. In order to reduce this time, one option is to execute the different plugin providers in parallel in a secondary thread and send to the main GUI thread the GUI tasks. Initial tests show that this can reduce the start-up time to 15 seconds (42% of reduction).

The main window will be the responsible to update all the plugin providers. It will delegate the responsibility to the class PluginSelectorWidget. This class adds an observer to each provider, that is derived from the class BaseProcessor. The provider will scan the plugins and when the plugins are going to be loaded, - this task should be executed by the main GUI thread - so it will call the function UpdateOuptut( ). The main GUI thread will receive the information about the plugin to load/unload using a blTagMap and call the function LoadPlugin/UnLoadPlugin for the current provider.

The information messages will be sent to the main GUI thread using the UpdateCallback class and the function AddInformationMessage( ).

Roadmap:

  • Remove current plugin name
  • Remove scan plugins from providermanager
  • Enable workflow perspective
  • Disable Multithread option
  • Generic descriptions
  • Unicore Provider

ENH #0402: Integrate MSV working area with metadata information

MSV working area allows visualization of data objects using tool tips and VTK buttons to navigate. Read more in MSV Plugin.

MSV working area with VTK buttons

ENH #0407: Add preview image for DataEntity

The interface class Core::DataEntityPreview is used for managing a preview image of a DataEntity. A concrete implementation is MITKPreview that uses wxImage to store/load/save the preview.

When a DataEntity is created, it searches the FactoryManager for an implementation of DataEntityPreview interface class and creates an instance.

The preview image is loaded/saved when the DataEntity is loaded/saved.

This class is used in MSV Plugin.