Difference between revisions of "Developer Meetings/20170502"
From Slicer Wiki
| Line 13: | Line 13: | ||
= Conclusion = | = 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. | |
= Appendix = | = Appendix = | ||
Revision as of 14:40, 2 May 2017
Home < Developer Meetings < 20170502
 |
If you would like to list your topic here, create a wiki account and edit this page You can join the hangout using http://bit.ly/slicer-hangout-kw. |
Contents
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.
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 namedslicerMacroBuildQtModule)
- Proposal: Rename CMake module from
SlicerMacroBuildQtModuletoslicerMacroBuildLoadableModule
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
