Difference between revisions of "Developer Meetings/20170502"
From Slicer Wiki
| (3 intermediate revisions by the same user not shown) | |||
| 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. | ||
| + | * 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 == | == Modules naming convention == | ||
| Line 40: | Line 41: | ||
* Base classes: | * Base classes: | ||
** c++ bridge [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/Base/QTGUI/qSlicerScriptedLoadableModule.h Base/QTGUI/qSlicerScriptedLoadableModule.h] | ** c++ bridge [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/Base/QTGUI/qSlicerScriptedLoadableModule.h Base/QTGUI/qSlicerScriptedLoadableModule.h] | ||
| − | ** python base [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/Base/Python/slicer/ScriptedLoadableModule.py | + | ** python base [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/Base/Python/slicer/ScriptedLoadableModule.py ScriptedLoadableModule.py] |
* CMake module named [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/CMake/SlicerMacroBuildScriptedModule.cmake SlicerMacroBuildScriptedModule.cmake] and provides macro <code>slicerMacroBuildScriptedModule</code> | * CMake module named [https://github.com/Slicer/Slicer/blob/fba6424b7d48fb4418295105894e317de6e850bf/CMake/SlicerMacroBuildScriptedModule.cmake SlicerMacroBuildScriptedModule.cmake] and provides macro <code>slicerMacroBuildScriptedModule</code> | ||
Latest revision as of 14:45, 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.
- 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 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
