Documentation/4.0/Developers/Tutorials/ExternalModuleWriting - Revision history

UpdateBot: Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2013-06-14T07:29:11Z

Prepend documentation/versioncheck template. See http://na-mic.org/Mantis/view.php?id=2887

2012-01-29T21:32:15Z

2012-01-29T21:31:26Z

Add links to tutorials

2012-01-29T21:24:05Z

add module wizard link

2011-11-21T15:24:25Z

2011-11-02T03:23:22Z

2011-11-02T03:18:12Z

2011-05-14T17:20:24Z

2011-05-14T16:01:03Z

2011-05-14T15:51:29Z

← Older revision		Revision as of 07:29, 14 June 2013
Line 1:		Line 1:
		+	<noinclude>{{documentation/versioncheck}}</noinclude>
	Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←		Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←

@@ Line 4: / Line 4: @@
 Consider also reading:
-*[[Media:QtPortInSlicer.ppt|QtPortInSlicer - How to write a module]]
+:[[Media:QtPortInSlicer.ppt|QtPortInSlicer - How to write a module]]
-*[[Documentation/{{documentation/version}}/Developers/Tutorials/ModuleWriting|How to write a module inside Slicer]]
+:[[Documentation/{{documentation/version}}/Developers/Tutorials/ModuleWriting|How to write a module inside Slicer]]
 * Create the skeleton code using the [[Documentation/{{documentation/version}}/Developers/ModuleWizard|module wizard]]

← Older revision		Revision as of 21:31, 29 January 2012
Line 2:		Line 2:

	This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.		This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.
		+
		+	Consider also reading:
		+	*[[Media:QtPortInSlicer.ppt\|QtPortInSlicer - How to write a module]]
		+	*[[Documentation/{{documentation/version}}/Developers/Tutorials/ModuleWriting\|How to write a module inside Slicer]]

	* Create the skeleton code using the [[Documentation/{{documentation/version}}/Developers/ModuleWizard\|module wizard]]		* Create the skeleton code using the [[Documentation/{{documentation/version}}/Developers/ModuleWizard\|module wizard]]

@@ Line 3: / Line 3: @@
 This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.
-* Create the skeleton code
+* Create the skeleton code using the [[Documentation/{{documentation/version}}/Developers/ModuleWizard|module wizard]]
    $ export SD=$HOME/build/slicer-4/Slicer4
    $ python ${SD}/Scripts/ModuleWizard.py \

← Older revision		Revision as of 15:24, 21 November 2011
Line 1:		Line 1:
−	[[Documentation/{{documentation/version}}/Developers\|~~Tutorials~~]]←	+	Back to [[Documentation/{{documentation/version}}/Developers\|Developers Information]]←

	This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.		This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.

← Older revision		Revision as of 03:23, 2 November 2011
Line 1:		Line 1:
−	[[~~Slicer4:QtPort\|QtSlicer]]~~/~~[[Slicer4:QtPort~~/~~Tutorials~~\|Tutorials]]←	+	[[Documentation/{{documentation/version}}/Developers\|Tutorials]]←

	This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.		This tutorial describes how to make a (Slicer4 / QT) loadable module that is compiled outside of the slicer build tree.

← Older revision	Revision as of 03:18, 2 November 2011
(No difference)

← Older revision		Revision as of 17:20, 14 May 2011
Line 68:		Line 68:

	[[File:ExternalModuleWriting_screenshot.png]]		[[File:ExternalModuleWriting_screenshot.png]]
		+
		+	* It is possible (with some work), to tell your program to build the module in your own directory instead of Slicer's. However, there is not yet any way to tell slicer to look in your own directory. So we leave the tutorial and await further developments.

← Older revision		Revision as of 16:01, 14 May 2011
Line 66:		Line 66:

	When you fire up slicer, you should see the module. For me, it looks like this:		When you fire up slicer, you should see the module. For me, it looks like this:
		+
		+	[[File:ExternalModuleWriting_screenshot.png]]

@@ Line 9: / Line 9: @@
         --target MY_MODULE_NAME \
         MY_MODULE_NAME
-* Set up your CMakeLists
+* Setting up your CMakeLists.txt
 ** [http://forge.abcd.harvard.edu/gf/project/plastimatch/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Fplastimatch%2Ftrunk%2Fcmake%2FFindSlicer.cmake Download FindSlicer.cmake]
-** Detect Slicer and add your module subdirectory
+** Edit CMakeLists.txt, and make it (1) detect Slicer, (2) load the Slicer "Use file", and (3) add your module subdirectory.
    find_package (Slicer QUIET)
    if (SLICER_FOUND)
@@ Line 19: / Line 19: @@
      endif ()
    endif ()
-* You might need to undo some of Slicer's settings.  If you don't think you need this, then you probably don't.  It depends how complicated your project is.  But if you need it, you can do something like this:
+* You might need to undo some of Slicer's settings.  If you don't think you need this, then you probably don't.  But if you need it, you can do something like this:
    if (Slicer_USE_FILE)
      get_directory_property (OLD_INCLUDE_DIR INCLUDE_DIRECTORIES)
@@ Line 64: / Line 64: @@
    ./lib/Slicer3/QTLoadableModules/libvtkSlicerMY_MODULE_NAMEModuleLogic.so
    ./lib/Slicer3/QTLoadableModules/libqSlicerMY_MODULE_NAMEModule.so