Developer Meetings/20170502 - Revision history

JChris.FillionR: /* Conclusion */

2017-05-02T14:45:10Z

Conclusion

JChris.FillionR: /* Conclusion */

2017-05-02T14:40:43Z

Conclusion

JChris.FillionR: /* Modules naming convention */

2017-05-02T14:09:34Z

Modules naming convention

JChris.FillionR at 13:31, 2 May 2017

2017-05-02T13:31:33Z

JChris.FillionR at 13:30, 2 May 2017

2017-05-02T13:30:59Z

JChris.FillionR: /* To Discuss */

2017-05-02T13:27:53Z

To Discuss

JChris.FillionR: Created page with "
{{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit t..."

2017-04-28T00:10:07Z

Created page with "<br> {{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit t..."

New page

<br>
{{mbox
| type = style
| text = If you would like to list your topic here, [[Special:UserLogin|create a wiki account]] and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit this page]<br>You can join the hangout using http://bit.ly/slicer-hangout-kw.
| image= [[File:smile.png|40px]]
}}
<br>

= To Discuss =

* Naming convention for Slicer modules. (Jc: Before the meeting I will had a table summarizing the current convention and proposed updates)

= Conclusion =

@@ Line 15: / Line 15: @@
 * 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 =

@@ Line 13: / Line 13: @@
 = 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 =

@@ Line 40: / Line 40: @@
 * Base classes:
 ** 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>

← Older revision		Revision as of 13:31, 2 May 2017
Line 16:		Line 16:


−	= ~~appendix~~ =	+	= Appendix =

	== Modules naming convention ==		== Modules naming convention ==

@@ Line 9: / Line 9: @@
 = To Discuss =
-* Naming convention for Slicer modules.
+* Naming convention for Slicer modules. See Appendix below
-= Modules naming convention =
+== Modules naming convention ==
 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]]
@@ Line 31: / Line 34: @@
 * '''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]]
@@ Line 41: / Line 44: @@
 * 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)]]
@@ Line 49: / Line 52: @@
 * 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

Developer Meetings/20170502 - Revision history

JChris.FillionR: /* Conclusion */

JChris.FillionR: /* Conclusion */

JChris.FillionR: /* Modules naming convention */

JChris.FillionR at 13:31, 2 May 2017

JChris.FillionR at 13:30, 2 May 2017

JChris.FillionR: /* To Discuss */

JChris.FillionR: Created page with " {{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit t..."

JChris.FillionR: Created page with "
{{mbox | type = style | text = If you would like to list your topic here, create a wiki account and [{{fullurl:{{FULLPAGENAME}}|action=edit}} edit t..."