2012 Summer Project Week Breakout Session:SlicerExtensions - Revision history

Pieper: /* Remarks */

2012-07-30T14:40:33Z

Remarks

2012-07-30T14:35:53Z

Step-by-step

2012-06-29T18:49:36Z

2012-06-19T14:42:24Z

Remarks

2012-06-18T22:11:24Z

Remarks

2012-06-18T22:08:25Z

Remarks

2012-06-18T21:55:39Z

Remarks

2012-06-18T21:49:02Z

Remarks

2012-06-18T21:46:55Z

2012-06-18T19:40:51Z

← Older revision		Revision as of 14:40, 30 July 2012
Line 94:		Line 94:
	* Category for work in progress extension ?		* Category for work in progress extension ?
	* Add stats/notes/indication to indicate active/inactive support of extension (e.g. 'last commit date', 'Dashboard link', '30-day development activity' (similar to GitHub's tracking))		* Add stats/notes/indication to indicate active/inactive support of extension (e.g. 'last commit date', 'Dashboard link', '30-day development activity' (similar to GitHub's tracking))
		+
		+	== Windows ==
		+
		+	If you do not have another python installation on your machine, you can use the python that is build with slicer to run the module creation script. The invocation from cmd prompt looks something like this:
		+
		+	d:\pieper\s4\Slicer>..\super\python-build\PCbuild\amd64\python.exe .\Utilities\Scripts\ModuleWizard.py --template ./Extensions/Testing/LoadableExtensionTemplate --target ./myloadable myloadable
		+
		+	From there you can use the regular windows procedures like cmake-gui and visual studio to build the extension.

@@ Line 35: / Line 35: @@
 == Step-by-step==
+(These instructions are for linux/mac environments - see windows notes in the remarks section below).
 * 1. Create base structure using ModuleWizard
 <pre>

← Older revision		Revision as of 18:49, 29 June 2012
Line 9:		Line 9:
	<big>An [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Extensions extension] could be seen as a delivery package bundling together one or more Slicer [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules].		<big>An [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Extensions extension] could be seen as a delivery package bundling together one or more Slicer [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules].

−	After installing an extension, the associated [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules] will be presented to the user as built-in ones</big>	+	After installing an extension, the associated [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules] will be presented to the user just like the built-in ones</big>

← Older revision		Revision as of 14:42, 19 June 2012
Line 93:		Line 93:
	* Make is clear that API key is sensitive		* Make is clear that API key is sensitive
	* Category for work in progress extension ?		* Category for work in progress extension ?
		+	* Add stats/notes/indication to indicate active/inactive support of extension (e.g. 'last commit date', 'Dashboard link', '30-day development activity' (similar to GitHub's tracking))

← Older revision		Revision as of 22:11, 18 June 2012
Line 92:		Line 92:
	* Add .gitignore to extension ... ?		* Add .gitignore to extension ... ?
	* Make is clear that API key is sensitive		* Make is clear that API key is sensitive
		+	* Category for work in progress extension ?

← Older revision		Revision as of 22:08, 18 June 2012
Line 91:		Line 91:
	* Remember Jim about the doc stuff: Migrate 1 module to extension to N ones		* Remember Jim about the doc stuff: Migrate 1 module to extension to N ones
	* Add .gitignore to extension ... ?		* Add .gitignore to extension ... ?
		+	* Make is clear that API key is sensitive

← Older revision		Revision as of 21:55, 18 June 2012
Line 90:		Line 90:
	* Label the newly installed modules .. or show a popup ?		* Label the newly installed modules .. or show a popup ?
	* Remember Jim about the doc stuff: Migrate 1 module to extension to N ones		* Remember Jim about the doc stuff: Migrate 1 module to extension to N ones
		+	* Add .gitignore to extension ... ?

← Older revision		Revision as of 21:49, 18 June 2012
Line 89:		Line 89:
	* Associated publications / Google scholar ?		* Associated publications / Google scholar ?
	* Label the newly installed modules .. or show a popup ?		* Label the newly installed modules .. or show a popup ?
		+	* Remember Jim about the doc stuff: Migrate 1 module to extension to N ones

← Older revision		Revision as of 21:46, 18 June 2012
Line 80:		Line 80:
	make ExperimentalUpload		make ExperimentalUpload
	</pre>		</pre>
		+
		+	= Remarks =
		+	* People seems to like the concept :)
		+	* Add institution to register box
		+	* No facebook / Linkedin instead
		+	* Search box
		+	* "I use it" button ?
		+	* Associated publications / Google scholar ?
		+	* Label the newly installed modules .. or show a popup ?

@@ Line 7: / Line 7: @@
-<big>An [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Extensions extension] could be seen as a delivery package bundling together one or more Slicer [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules]. After installing an extension, the associated [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules] will be presented to the user as built-in ones</big>
+<big>An [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Extensions extension] could be seen as a delivery package bundling together one or more Slicer [http://wiki.slicer.org/slicerWiki/index.php/Documentation/4.1/Developers/Modules modules].
@@ Line 39: / Line 41: @@
 </pre>
-* 2. Check that file have been created
+* 2. Check that expected files have been created
 <pre>
 cd ..