Developer Meetings/20170502

To Discuss

• Naming convention for Slicer modules. See Appendix below

Conclusion

• Signing app: We could automatically sign but do we want to give user a false impression of "security" ?
• Qt5: Good progress from Hina. Slicer Web widget is on the way to work with web engine.
• Nightly MacOSX issue: We will roll back to Python 2.7.12 that doesn't depend on OpenSSL 1.0.0 (see https://discourse.slicer.org/t/multiple-startup-errors-and-no-simpleitk-in-may-1-nightly-on-mac/231/10?u=jcfr)

Appendix

Modules naming convention

In Slicer we have the following modules

Loadable modules

C++

• Found on the wiki as Loadable_Modules

• Base class: Base/QTGUI/qSlicerLoadableModule.h

• Main CMake module named SlicerMacroBuildQtModule.cmake and provides macro slicerMacroBuildLoadableModule (along with deprecated one named slicerMacroBuildQtModule)

• Proposal: Rename CMake module from SlicerMacroBuildQtModule to slicerMacroBuildLoadableModule

Python

• Found on the wiki as [Modules]

• Base classes:
  • c++ bridge Base/QTGUI/qSlicerScriptedLoadableModule.h
  • python base ScriptedLoadableModule.py

• CMake module named SlicerMacroBuildScriptedModule.cmake and provides macro slicerMacroBuildScriptedModule

CLI module

C++

• Found on the wiki as [Line Interface (CLI)]

• CMake macro: SEMMacroBuildCLI

Python

• Support classes already implemented, support to be added in Slicer very soon. It will allow to write CLI in python like this one: https://github.com/DigitalSlideArchive/HistomicsTK/tree/master/server/NucleiDetection