Difference between revisions of "Slicer3:Loadable Modules:Phase1"

Latest revision as of 17:50, 10 July 2017

Home < Slicer3:Loadable Modules:Phase1

Note: We are migrating this content to the slicer.org domain - The newer page is here

@@ Line 1: / Line 1: @@
-From [[Slicer3:Loadable_Modules]]:
+<big>'''Note:''' We are migrating this content to the slicer.org domain - <font color="orange">The newer page is [https://www.slicer.org/wiki/Slicer3:Loadable_Modules:Phase1  here]</font></big>
-    * runtime module discovery
-    * module template
-    * like CommandLineModuleFactory
-----
-Starting at ~900 in Applications/GUI/Slicer3.cxx, static modules load occurs.
-Using vtkSys tools to list shared libraries present.  Use itk::DyanmicLoader to open libraries and call our specified entry points.
-The actions taken for each module to be added could be queried from the found shared library using a LoadableModuleInfo class. Some of the information a library should provide:
-* vtkSlicerLogic pointer (maybe this is one of the defined entry points for a loadable module)
-* methods to call on the Logic pointer
-* vtkSlicerModulesGUI pointer (ditto)
-* methods to call on the GUI pointer
-* module name
-LoadableModuleFactory (ala Libs/ModuleDescriptionParser/ModuleFactory.cxx) handles this.  Looks like ModuleFactory::ScanForSharedObjectModules does something very similar.