Internal:SlicerExtensions - Revision history

Angelos: /* APBNRR Extension */

2018-08-29T01:29:06Z

APBNRR Extension

← Older revision		Revision as of 20:29, 28 August 2018
Line 13:		Line 13:

	== APBNRR Extension ==		== APBNRR Extension ==
	Status: <span style="color:red">TRANSITIONING ~~CODE~~ TO A LOADABLE MODULE</span>		Status: <span style="color:red">TRANSITIONING LOGIC TO A LOADABLE MODULE</span>

	Due to the conflict of ITKDev and the ITK version of Slicer, creating a locally executable APBNRR module for Slicer is not conventionally possible.		Due to the conflict of ITKDev and the ITK version of Slicer, creating a locally executable APBNRR module for Slicer is not conventionally possible.

Angelos: /* APBNRR Extension */

2018-08-29T01:28:37Z

APBNRR Extension

← Older revision		Revision as of 20:28, 28 August 2018
Line 13:		Line 13:

	== APBNRR Extension ==		== APBNRR Extension ==
	Status: <span style="color:red">~~IMPLEMENTING LOCAL INTERMEDIARY~~ MODULE ~~LOGIC~~</span>		Status: <span style="color:red">TRANSITIONING CODE TO A LOADABLE MODULE</span>

	Due to the conflict of ITKDev and the ITK version of Slicer, creating a locally executable APBNRR module for Slicer is not conventionally possible.		Due to the conflict of ITKDev and the ITK version of Slicer, creating a locally executable APBNRR module for Slicer is not conventionally possible.

Angelos: /* Scriptable vs Loadable Module */

2018-08-29T01:27:13Z

Scriptable vs Loadable Module

← Older revision		Revision as of 20:27, 28 August 2018
Line 51:		Line 51:

	* A scriptable module is coded with Python		* A scriptable module is coded with Python
	* A scriptable module is ~~simpler~~ and ~~faster~~ to develop and maintain		* A scriptable module is simple and fast to develop and maintain
	* A scriptable module has control over anything that Slicer wraps with Python		* A scriptable module has control over anything that Slicer wraps with Python
	* A scriptable module is great for prototypes and non-computationally intensive tasks		* A scriptable module is great for prototypes and non-computationally intensive tasks

Angelos: /* Scriptable vs Loadable Module */

2018-08-29T01:27:01Z

Scriptable vs Loadable Module

← Older revision		Revision as of 20:27, 28 August 2018
Line 51:		Line 51:

	* A scriptable module is coded with Python		* A scriptable module is coded with Python
	* A scriptable module is simpler and faster to develop		* A scriptable module is simpler and faster to develop and maintain
	* A scriptable module has control over anything that Slicer wraps with Python		* A scriptable module has control over anything that Slicer wraps with Python
	* A scriptable module is great for prototypes and non-computationally intensive tasks		* A scriptable module is great for prototypes and non-computationally intensive tasks
Line 62:		Line 62:
	* A loadable module has high performance and is well suited for computationally intensive tasks		* A loadable module has high performance and is well suited for computationally intensive tasks
	* A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them		* A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them


	=== Local Intermediary Module ===		=== Local Intermediary Module ===

Angelos: /* APBNRR Extension */

2018-08-29T01:25:21Z

APBNRR Extension

← Older revision		Revision as of 20:25, 28 August 2018
Line 62:		Line 62:
	* A loadable module has high performance and is well suited for computationally intensive tasks		* A loadable module has high performance and is well suited for computationally intensive tasks
	* A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them		* A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them


	=== Local Intermediary Module ===		=== Local Intermediary Module ===

Angelos: /* APBNRR Extension */

2018-08-29T01:25:08Z

APBNRR Extension

@@ Line 20: / Line 20: @@
 The skeleton of the intermediary module can also be reused for the remote execution module to save time, modified to accommodate remote execution and communicate via SSH.
 === Scriptable to Loadable Module Transition Checklist ===
@@ Line 41: / Line 62: @@
 * A loadable module has high performance and is well suited for computationally intensive tasks
 * A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them
 === Local Intermediary Module ===

Angelos: /* Scriptable vs Loadable Module */

2018-08-29T01:23:29Z

Scriptable vs Loadable Module

← Older revision		Revision as of 20:23, 28 August 2018
Line 33:		Line 33:
	* A scriptable module has control over anything that Slicer wraps with Python		* A scriptable module has control over anything that Slicer wraps with Python
	* A scriptable module is great for prototypes and non-computationally intensive tasks		* A scriptable module is great for prototypes and non-computationally intensive tasks
			* A scriptable module usually works with many Slicer releases out of the box

	'''''A loadable module is a Slicer module that is a shared object library loaded by Slicer on run-time which has deep control over Slicer.'''''		'''''A loadable module is a Slicer module that is a shared object library loaded by Slicer on run-time which has deep control over Slicer.'''''
Line 39:		Line 40:
	* A loadable module has deep control over Slicer, including full control of the UI		* A loadable module has deep control over Slicer, including full control of the UI
	* A loadable module has high performance and is well suited for computationally intensive tasks		* A loadable module has high performance and is well suited for computationally intensive tasks
			* A loadable module requires recompilation with specific Slicer releases and perhaps modification to support them

	=== Checklist ===		=== Checklist ===

Angelos: /* Scriptable vs Loadable Module */

2018-08-29T01:20:43Z

Scriptable vs Loadable Module

← Older revision		Revision as of 20:20, 28 August 2018
Line 27:		Line 27:

	==== Scriptable vs Loadable Module ====		==== Scriptable vs Loadable Module ====
	'''A scriptable module is a Slicer module that is essentially a Python script utilizing PyQt to extend Slicer's UI and functionality.'''		'''''A scriptable module is a Slicer module that is essentially a Python script utilizing PyQt to extend Slicer's UI and functionality.'''''

	* A scriptable module is coded with Python		* A scriptable module is coded with Python
Line 34:		Line 34:
	* A scriptable module is great for prototypes and non-computationally intensive tasks		* A scriptable module is great for prototypes and non-computationally intensive tasks

	'''A loadable module is a Slicer module that is a shared object library loaded by Slicer on run-time which has deep control over Slicer.'''		'''''A loadable module is a Slicer module that is a shared object library loaded by Slicer on run-time which has deep control over Slicer.'''''
	* A loadable module is coded with C++		* A loadable module is coded with C++
	* A loadable module is harder to implement and maintain		* A loadable module is harder to implement and maintain

Angelos: /* Scriptable vs Loadable Module */

2018-08-29T01:20:21Z

Scriptable vs Loadable Module

← Older revision		Revision as of 20:20, 28 August 2018
Line 27:		Line 27:

	==== Scriptable vs Loadable Module ====		==== Scriptable vs Loadable Module ====
			'''A scriptable module is a Slicer module that is essentially a Python script utilizing PyQt to extend Slicer's UI and functionality.'''

	* A scriptable module is coded with Python		* A scriptable module is coded with Python
	* A scriptable module is simpler and faster to develop		* A scriptable module is simpler and faster to develop
Line 32:		Line 34:
	* A scriptable module is great for prototypes and non-computationally intensive tasks		* A scriptable module is great for prototypes and non-computationally intensive tasks

			'''A loadable module is a Slicer module that is a shared object library loaded by Slicer on run-time which has deep control over Slicer.'''
	* A loadable module is coded with C++		* A loadable module is coded with C++
	* A loadable module is harder to implement and maintain		* A loadable module is harder to implement and maintain

Angelos: /* Checklist */

2018-08-29T01:17:03Z

Checklist

← Older revision		Revision as of 20:17, 28 August 2018
Line 47:		Line 47:
	Note: Full portability may not be possible due to some system libraries like LIBC. If there are errors, the user can compile APBNRR themselves and the intermediary module should still work using it. I later plan to utilize the SuperBuild scripts I developed for the earlier design in this portion to create an automatic build system for APBNRR.		Note: Full portability may not be possible due to some system libraries like LIBC. If there are errors, the user can compile APBNRR themselves and the intermediary module should still work using it. I later plan to utilize the SuperBuild scripts I developed for the earlier design in this portion to create an automatic build system for APBNRR.
	* Implement intermediary "executor" loadable module in Slicer for local execution of APBNRR		* Implement intermediary "executor" loadable module in Slicer for local execution of APBNRR
			** [<span style="color:blue">IN PROGRESS</span>] Transition to loadable module
	** [<span style="color:green">DONE</span>] Design UI		** [<span style="color:green">DONE</span>] Design UI
	** [<span style="color:green">DONE</span>] Implement UI		** [<span style="color:green">DONE</span>] Implement UI