Difference between revisions of "Developer Meetings/20150407"
From Slicer Wiki
m |
m |
||
| Line 10: | Line 10: | ||
== Conclusions == | == Conclusions == | ||
| + | * Python module infrastructure improvement | ||
| + | ** Since commit [http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=24155 r24155], scripted module are imported as python module. | ||
| + | ** The next change will be to support loading of slicer scripted module as regular python module (a folder with __init__.py) | ||
| + | ** A landmark file could be added to scripted module folder (slicer.json or slicer-module.json) | ||
| + | ** This landmark file could then be used to speedup the startup time by loading only the core scripted module. | ||
| + | |||
| + | * CLI and loadable module infrastructure improvement | ||
| + | ** Similarly to scripted module, the Slicer module loader could look for a landmark file | ||
Revision as of 19:13, 7 April 2015
Home < Developer Meetings < 20150407Contents
Updates
To discuss
- Create a new release: 4.4.1 or 4.5 ?
- Failing test: EMSegCL_Task_HumanEye_BRAINS_small
- Issue witg DataProbeLib
Todo
Conclusions
- Python module infrastructure improvement
- Since commit r24155, scripted module are imported as python module.
- The next change will be to support loading of slicer scripted module as regular python module (a folder with __init__.py)
- A landmark file could be added to scripted module folder (slicer.json or slicer-module.json)
- This landmark file could then be used to speedup the startup time by loading only the core scripted module.
- CLI and loadable module infrastructure improvement
- Similarly to scripted module, the Slicer module loader could look for a landmark file
