Difference between revisions of "Developer Meetings/20170502"

From Slicer Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 9: Line 9:
 
= To Discuss =
 
= To Discuss =
  
* Naming convention for Slicer modules.
+
* 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 =
+
== Modules naming convention ==
  
 
In Slicer we have the following modules
 
In Slicer we have the following modules
  
== Loadable modules ==
+
=== Loadable modules ===
  
=== C++ ===
+
==== C++ ====
  
 
* Found on the wiki as [[Documentation/Nightly/Developers/Modules#Loadable_Modules|Loadable_Modules]]
 
* Found on the wiki as [[Documentation/Nightly/Developers/Modules#Loadable_Modules|Loadable_Modules]]
Line 31: Line 35:
 
* '''Proposal''': Rename CMake module from <code>SlicerMacroBuildQtModule</code> to <code>slicerMacroBuildLoadableModule</code>
 
* '''Proposal''': Rename CMake module from <code>SlicerMacroBuildQtModule</code> to <code>slicerMacroBuildLoadableModule</code>
  
=== Python ===
+
==== Python ====
  
 
* Found on the wiki as [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Modules#Scripted_Modules|Scripted Modules]]
 
* Found on the wiki as [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Modules#Scripted_Modules|Scripted Modules]]
Line 37: 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 Base/QTGUI/ScriptedLoadableModule.h]
+
** 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>
  
== CLI module ==
+
=== CLI module ===
  
=== C++ ===
+
==== C++ ====
  
 
* Found on the wiki as [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Modules#Command_Line_Interface_.28CLI.29|Command Line Interface (CLI)]]
 
* Found on the wiki as [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Modules#Command_Line_Interface_.28CLI.29|Command Line Interface (CLI)]]
Line 49: Line 53:
 
* CMake macro: <code>SEMMacroBuildCLI</code>
 
* CMake macro: <code>SEMMacroBuildCLI</code>
  
=== Python ===
+
==== 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
 
* 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
 
= Conclusion =
 

Latest revision as of 14:45, 2 May 2017

Home < Developer Meetings < 20170502



To Discuss

  • Naming convention for Slicer modules. See Appendix below


Conclusion

Appendix

Modules naming convention

In Slicer we have the following modules

Loadable modules

C++

  • 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

CLI module

C++

  • CMake macro: SEMMacroBuildCLI

Python